<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Do not modify this file directly. Instead, copy entries that you -->
<!-- wish to modify from this file into mapred-site.xml and change them -->
<!-- there. If mapred-site.xml does not already exist, create it. -->
<configuration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="configuration.xsd">
    <property>
        <name>hadoop.jobtracker.memory</name>
        <value>4096</value>
        <valuetype>Integer</valuetype>
        <group>jobtracker</group>
        <definition>
            <en>JobTracker server memory size</en>
        </definition>
        <type>1</type>
        <automatic>true</automatic>
        <reserved>true</reserved>
        <description>
            <en>Default size for jobtracker server memory.</en>
        </description>
    </property>
    <property>
        <name>hadoop.tasktracker.slot.memory</name>
        <value>4096</value>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>Total memory size for tasktracker map and reduce slot</en>
        </definition>
        <type>1</type>
        <automatic>true</automatic>
        <reserved>true</reserved>
        <description>
            <en>Total memory size for tasktracker map and reduce slot.</en>
        </description>
    </property>
    <property>
        <name>hadoop.tasktracker.memory</name>
        <value>4096</value>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>Default size for tasktracker server memory</en>
        </definition>
        <type>1</type>
        <automatic>true</automatic>
        <reserved>true</reserved>
        <description>
            <en>Default size for tasktracker server memory.</en>
        </description>
    </property>
    <property>
        <name>hadoop.job.history.location</name>
        <value></value>
        <allowempty>true</allowempty>
        <valuetype>String</valuetype>
        <group>basic</group>
        <definition>
            <en>job history location</en>
        </definition>
        <description>
            <en> If job tracker is static the history files are stored
  in this single well known place. If No value is set here, by default,
  it is in the local file system at ${hadoop.log.dir}/history.
  </en>
        </description>
    </property>
    <property>
        <name>hadoop.job.history.user.location</name>
        <value></value>
        <allowempty>true</allowempty>
        <valuetype>String</valuetype>
        <group>basic</group>
        <definition>
            <en>user specified history location</en>
        </definition>
        <description>
            <en> User can specify a location to store the history files of
  a particular job. If nothing is specified, the logs are stored in
  output directory. The files are stored in "_logs/history/" in the directory.
  User can stop logging by giving the value "none".
  </en>
        </description>
    </property>
    <property>
        <name>mapred.job.tracker.history.completed.location</name>
        <value></value>
        <allowempty>true</allowempty>
        <valuetype>String</valuetype>
        <group>basic</group>
        <definition>
            <en>The completed job history files location</en>
        </definition>
        <description>
            <en> The completed job history files are stored at this single well
  known location. If nothing is specified, the files are stored at
  ${hadoop.job.history.location}/done.
  </en>
        </description>
    </property>
    <!-- i/o properties -->
    <property>
        <name>io.sort.factor</name>
        <value>10</value>
        <intel_default>10</intel_default>
        <recommendation>100</recommendation>
        <valuetype>Integer</valuetype>
        <group>perf</group>
        <definition>
            <en>IO sort factor</en>
        </definition>
        <description>
            <en>The number of streams to merge at once while sorting
  files.  This determines the number of open file handles.</en>
        </description>
    </property>
    <property>
        <name>io.sort.mb</name>
        <value>100</value>
        <intel_default>100</intel_default>
                <recommendation>200</recommendation>
        <valuetype>Integer</valuetype>
        <group>perf</group>
        <definition>
            <en>Total amount of buffer memory to use while sorting
  files,</en>
        </definition>
        <description>
            <en>The total amount of buffer memory to use while sorting
  files, in megabytes.  By default, gives each merge stream 1MB, which
  should minimize seeks.</en>
        </description>
    </property>
    <property>
        <name>io.sort.record.percent</name>
        <value>0.05</value>
        <valuetype>Float</valuetype>
        <group>perf</group>
        <definition>
            <en>The percentage of io.sort.mb dedicated to tracking record
  boundaries</en>
        </definition>
        <description>
            <en>The percentage of io.sort.mb dedicated to tracking record
  boundaries. Let this value be r, io.sort.mb be x. The maximum number
  of records collected before the collection thread must block is equal
  to (r * x) / 4</en>
        </description>
    </property>
    <property>
        <name>io.sort.spill.percent</name>
        <value>0.80</value>
        <valuetype>Float</valuetype>
        <group>perf</group>
        <definition>
            <en>buffer limit</en>
        </definition>
        <description>
            <!-- not sure what it means -->
            <en>The soft limit in either the buffer or record collection
  buffers. Once reached, a thread will begin to spill the contents to disk
  in the background. Note that this does not imply any chunking of data to
  the spill. A value less than 0.5 is not recommended.</en>
        </description>
    </property>
    <property>
        <name>io.map.index.skip</name>
        <value>0</value>
        <valuetype>Integer</valuetype>
        <group>io</group>
        <definition>
            <en>Number of index entries to skip between each entry</en>
        </definition>
        <description>
            <en>Number of index entries to skip between each entry.
  Zero by default. Setting this to values larger than zero can
  facilitate opening large map files using less memory.</en>
        </description>
    </property>
    <property>
        <name>mapred.job.tracker</name>
        <enable>false</enable>
        <value>local</value>
        <recommendation></recommendation>
        <allowempty>true</allowempty>
        <valuetype>String</valuetype>
        <group>jobtracker</group>
        <definition>
            <en>The host and port that the MapReduce job tracker runs
  at</en>
        </definition>
        <description>
            <en>The host that the MapReduce job tracker runs
  at.  If "local", then jobs are run in-process as a single map
  and reduce task.
  </en>
        </description>
    </property>
  <property>
    <name>mapred.jobtracker</name>
    <readonly>true</readonly>
    <value></value>
    <allowempty>true</allowempty>
    <valuetype>String</valuetype>
    <global>true</global>
    <group>jobtracker</group>
    <definition>
      <en>The address that the job tracker runs at</en>
    </definition>
    <sectionname>directory</sectionname>
    <description>
      <en>The host and port that the MapReduce job tracker runs
  at.  If "local", then jobs are run in-process as a single map
  and reduce task.
  </en>
    </description>
    <form>TextItem</form>
  </property>
    <property>
        <name>mapred.jobtracker.port</name>
        <value>54311</value>
        <valuetype>Integer</valuetype>
        <group>jobtracker</group>
        <definition>
            <en>The port that the MapReduce job tracker runs
  at</en>
        </definition>
        <global>true</global>
        <description>
            <en>The port that the MapReduce job tracker runs
  at.  If "local", then jobs are run in-process as a single map
  and reduce task.
  </en>
        </description>
    </property>
    <property>
        <name>hadoop.jobtracker.thrift.port</name>
        <value>9290</value>
        <valuetype>Integer</valuetype>
        <group>jobtracker</group>
        <definition>
            <en>The port for jobtracker thrift server.</en>
        </definition>
        <global>true</global>
        <description>
            <en>The port for jobtracker thrift server.</en>
        </description>
    </property>
    <property>
        <name>mapred.job.tracker.http.address</name>
        <value>0.0.0.0:50030</value>
        <valuetype>String</valuetype>
        <group>jobtracker</group>
        <definition>
            <en>The job tracker http server address and port</en>
        </definition>
        <description>
            <en>
    The job tracker http server address and port the server will listen on.
    If the port is 0 then the server will start on a free port.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.job.tracker.handler.count</name>
        <value>10</value>
        <intel_default>10</intel_default>
                 <recommendation>60</recommendation>
        <valuetype>Integer</valuetype>
        <group>jobtracker</group>
        <definition>
            <en>The number of server threads for the JobTracker.</en>
        </definition>
        <description>
            <en>
    The number of server threads for the JobTracker. This should be roughly
    4% of the number of tasktracker nodes.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.task.tracker.report.address</name>
        <value>127.0.0.1:0</value>
        <valuetype>String</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>The interface and port that task tracker server listens on</en>
        </definition>
        <description>
            <en>The interface and port that task tracker server listens on.
  Since it is only connected to by the tasks, it uses the local interface.
  EXPERT ONLY. Should only be changed if your host does not have the loopback
  interface.</en>
        </description>
    </property>
    <property>
        <name>mapred.local.dir</name>
        <value>${hadoop.tmp.dir}/mapred/local</value>
        <recommendation></recommendation>
        <allowempty>true</allowempty>
        <valuetype>Directory</valuetype>
        <group>basic</group>
        <definition>
            <en>MapReduce local directory</en>
        </definition>
        <script>'export dirs=`ruby /usr/lib/intelcloud/scripts/mounts.rb 2>/dev/null`;if [ "$dirs" == "" ]; then echo "/hadoop/mapred"; else for dir in $dirs; do echo $dir/hadoop/mapred; done; fi' </script>
        <type>2</type>
        <description>
            <en>The local directory where MapReduce stores intermediate
  data files.  May be a comma-separated list of
  directories on different devices in order to spread disk i/o.
  Directories that do not exist are ignored.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.system.dir</name>
        <value>${hadoop.tmp.dir}/mapred/system</value>
        <valuetype>Directory</valuetype>
        <group>basic</group>
        <definition>
            <en>The directory where MapReduce stores control files.</en>
        </definition>
        <enable>false</enable>
        <description>
            <en>The directory where MapReduce stores control files.</en>
        </description>
    </property>
    <property>
        <name>mapreduce.jobtracker.staging.root.dir</name>
        <value>${hadoop.tmp.dir}/mapred/staging</value>
        <valuetype>Directory</valuetype>
        <group>basic</group>
        <definition>
            <en>The root of the staging area for users' job files</en>
        </definition>
        <enable>false</enable>
        <description>
            <en>The root of the staging area for users' job files
  In practice, this should be the directory where users' home
  directories are located (usually /user)
  </en>
        </description>
    </property>
    <property>
        <name>mapred.temp.dir</name>
        <value>${hadoop.tmp.dir}/mapred/temp</value>
        <valuetype>Directory</valuetype>
        <group>basic</group>
        <definition>
            <en>A shared directory for temporary files.</en>
        </definition>
        <enable>false</enable>
        <description>
            <en>A shared directory for temporary files.</en>
        </description>
    </property>
    <property>
        <name>mapred.local.dir.minspacestart</name>
        <value>0</value>
        <valuetype>Integer</valuetype>
        <group>basic</group>
        <definition>
            <en>minimum space in mapred.local.dir to start task</en>
        </definition>
        <description>
            <en>If the space in mapred.local.dir drops under this,
  do not ask for more tasks. Value in bytes.</en>
        </description>
    </property>
    <property>
        <name>mapred.local.dir.minspacekill</name>
        <value>0</value>
        <valuetype>Integer</valuetype>
        <group>basic</group>
        <definition>
            <en>mapred.local.dir minimum space kill</en>
        </definition>
        <description>
            <en>If the space in mapred.local.dir drops under this,
    do not ask more tasks until all the current ones have finished and
    cleaned up. Also, to save the rest of the tasks we have running,
    kill one of them, to clean up some space. Start with the reduce tasks,
    then go with the ones that have finished the least.
    Value in bytes.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.tasktracker.expiry.interval</name>
        <value>600000</value>
        <intel_default>600000</intel_default>
                <recommendation>180000</recommendation>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>TaskTracker expiry interval</en>
        </definition>
        <description>
            <en>Expert: The time-interval, in miliseconds, after which
  a tasktracker is declared 'lost' if it doesn't send heartbeats.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.tasktracker.instrumentation</name>
        <enable>false</enable>
        <value>org.apache.hadoop.mapred.TaskTrackerMetricsSource</value>
        <valuetype>Class</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>TaskTracker instrumentation class</en>
        </definition>
        <description>
            <en>Expert: The instrumentation class to associate with each TaskTracker.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.tasktracker.resourcecalculatorplugin</name>
        <value></value>
        <allowempty>true</allowempty>
        <valuetype>String</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>tasktracker resource calculator plugin</en>
        </definition>
        <description>
            <en>
   Name of the class whose instance will be used to query resource information
   on the tasktracker.The class must be an instance of
   org.apache.hadoop.util.ResourceCalculatorPlugin. If the value is null, the
   tasktracker attempts to use a class appropriate to the platform.
   Currently, the only platform supported is Linux.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.tasktracker.taskmemorymanager.monitoring-interval</name>
        <value>5000</value>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>TaskTracker monitoring interval</en>
        </definition>
        <description>
            <en>The interval, in milliseconds, for which the tasktracker waits
   between two cycles of monitoring its tasks' memory usage. Used only if
   tasks' memory management is enabled via mapred.tasktracker.tasks.maxmemory.
   </en>
        </description>
    </property>
    <property>
        <name>mapred.tasktracker.tasks.sleeptime-before-sigkill</name>
        <value>5000</value>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>TaskTracker sleeptime before sending a SIGKILL</en>
        </definition>
        <description>
            <en>The time, in milliseconds, the tasktracker waits for sending a
  SIGKILL to a process, after it has been sent a SIGTERM.</en>
        </description>
    </property>
    <property>
        <name>mapred.map.tasks</name>
        <value>2</value>
        <valuetype>Integer</valuetype>
        <group>map</group>
        <definition>
            <en>map count</en>
        </definition>
        <description>
            <en>The default number of map tasks per job.
  Ignored when mapred.job.tracker is "local".
  </en>
        </description>
    </property>
    <property>
        <name>mapred.reduce.tasks</name>
        <value>1</value>
        <valuetype>Integer</valuetype>
        <group>reduce</group>
        <definition>
            <en>reduce count</en>
        </definition>
        <description>
            <!-- in a single wave? -->
            <en>The default number of reduce tasks per job. Typically set to 99%
  of the cluster's reduce capacity, so that if a node fails the reduces can
  still be executed in a single wave.
  Ignored when mapred.job.tracker is "local".
  </en>
        </description>
    </property>
    <property>
        <name>mapreduce.tasktracker.outofband.heartbeat</name>
        <value>false</value>
        <recommendation>true</recommendation>
        <valuetype>Boolean</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>TaskTracker out-of-band heartbeat</en>
        </definition>
        <description>
            <en>Expert: Set this to true to let the tasktracker send an
  out-of-band heartbeat on task-completion for better latency.
  </en>
        </description>
    </property>
    <property>
        <name>mapreduce.tasktracker.outofband.heartbeat.damper</name>
        <value>1000000</value>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>out-of-band heartbeat damper</en>
        </definition>
        <description>
            <en>When out-of-band heartbeats are enabled, provides
  damping to avoid overwhelming the JobTracker if too many out-of-band
  heartbeats would occur. The damping is calculated such that the
  heartbeat interval is divided by (T*D + 1) where T is the number
  of completed tasks and D is the damper value.
  Setting this to a high value like the default provides no damping --
  as soon as any task finishes, a heartbeat will be sent. Setting this
  parameter to 0 is equivalent to disabling the out-of-band heartbeat feature.
  A value of 1 would indicate that, after one task has completed, the
  time to wait before the next heartbeat would be 1/2 the usual time.
  After two tasks have finished, it would be 1/3 the usual time, etc.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.jobtracker.restart.recover</name>
        <value>false</value>
        <valuetype>Boolean</valuetype>
        <group>job</group>
        <definition>
            <en>Whether enable job recovery</en>
        </definition>
        <description>
            <en>"true" to enable (job) recovery upon restart,
               "false" to start afresh
  </en>
        </description>
    </property>
    <property>
        <name>mapred.jobtracker.job.history.block.size</name>
        <value>3145728</value>
        <valuetype>Integer</valuetype>
        <group>job</group>
        <definition>
            <en>The block size of the job history file</en>
        </definition>
        <description>
            <en>The block size of the job history file. Since the job recovery
               uses job history, its important to dump job history to disk as
               soon as possible. Note that this is an expert level parameter.
               The default value is set to 3 MB.
  </en>
        </description>
    </property>
    <property>
        <name>mapreduce.job.split.metainfo.maxsize</name>
        <value>10000000</value>
        <valuetype>Integer</valuetype>
        <group>job</group>
        <definition>
            <en>The maximum permissible size of the split metainfo file</en>
        </definition>
        <description>
            <en>The maximum permissible size of the split metainfo file.
  The JobTracker won't attempt to read split metainfo files bigger than
  the configured value.
  No limits if set to -1.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.jobtracker.taskScheduler</name>
        <enable>false</enable>
        <value>org.apache.hadoop.mapred.JobQueueTaskScheduler</value>
        <valuetype>Class</valuetype>
        <group>basic</group>
        <definition>
            <en>The class responsible for scheduling the tasks.</en>
        </definition>
        <description>
            <en>The class responsible for scheduling the tasks.</en>
        </description>
    </property>
    <property>
        <name>mapred.jobtracker.taskScheduler.maxRunningTasksPerJob</name>
        <value></value>
        <allowempty>true</allowempty>
        <valuetype>Integer</valuetype>
        <group>job</group>
        <definition>
            <en>The maximum number of running tasks for a job before
  it gets preempted</en>
        </definition>
        <enable>false</enable>
        <description>
            <en>The maximum number of running tasks for a job before
  it gets preempted. No limits if undefined.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.map.max.attempts</name>
        <value>4</value>
        <valuetype>Integer</valuetype>
        <group>map</group>
        <definition>
            <en>Map maximum attempt times</en>
        </definition>
        <description>
            <en>Expert: The maximum number of attempts per map task.
  In other words, framework will try to execute a map task these many number
  of times before giving up on it.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.reduce.max.attempts</name>
        <value>4</value>
        <valuetype>Integer</valuetype>
        <group>reduce</group>
        <definition>
            <en>Reduce maximum attempt times</en>
        </definition>
        <description>
            <en>Expert: The maximum number of attempts per reduce task.
  In other words, framework will try to execute a reduce task these many number
  of times before giving up on it.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.reduce.parallel.copies</name>
        <value>5</value>
        <recommendation>20</recommendation>
        <valuetype>Integer</valuetype>
        <group>perf</group>
        <definition>
            <en>The default number of parallel transfers run by reduce
  during the copy(shuffle) phase</en>
        </definition>
        <description>
            <en>The default number of parallel transfers run by reduce
  during the copy(shuffle) phase.
  </en>
        </description>
    </property>
    <property>
        <name>mapreduce.reduce.shuffle.maxfetchfailures</name>
        <value>10</value>
        <valuetype>Integer</valuetype>
        <group>reduce</group>
        <definition>
            <en>reducer maximum fetch failures</en>
        </definition>
        <description>
            <en>The maximum number of times a reducer tries to
  fetch a map output before it reports it.
</en>
        </description>
    </property>
    <property>
        <name>mapreduce.reduce.shuffle.connect.timeout</name>
        <value>180000</value>
        <valuetype>Integer</valuetype>
        <group>reduce</group>
        <definition>
            <en>reducer connect timeout</en>
        </definition>
        <description>
            <en>Expert: The maximum amount of time (in milli seconds) a reduce
  task spends in trying to connect to a tasktracker for getting map output.
  </en>
        </description>
    </property>
    <property>
        <name>mapreduce.reduce.shuffle.read.timeout</name>
        <value>180000</value>
        <valuetype>Integer</valuetype>
        <group>reduce</group>
        <definition>
            <en>reducer read timeout</en>
        </definition>
        <description>
            <en>Expert: The maximum amount of time (in milli seconds) a reduce
  task waits for map output data to be available for reading after obtaining
  connection.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.task.timeout</name>
        <value>600000</value>
                <recommendation>180000</recommendation>
        <valuetype>Integer</valuetype>
        <group>basic</group>
        <definition>
            <en>task timeout value</en>
        </definition>
        <description>
            <en>The number of milliseconds before a task will be
  terminated if it neither reads an input, writes an output, nor
  updates its status string.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.tasktracker.map.tasks.maximum</name>
        <value>2</value>
        <recommendation></recommendation>
        <allowempty>true</allowempty>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>The maximum number of map tasks that will be run
  simultaneously by a task tracker</en>
        </definition>
        <automatic>true</automatic>
        <script>'cat /proc/cpuinfo | grep processor | wc -l'</script>
        <type>2</type>
        <description>
            <en>The maximum number of map tasks that will be run
  simultaneously by a task tracker.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.tasktracker.reduce.tasks.maximum</name>
        <value>2</value>
        <recommendation></recommendation>
        <allowempty>true</allowempty>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>The maximum number of reduce tasks that will be run
  simultaneously by a task tracker.</en>
        </definition>
        <automatic>true</automatic>
        <script>'echo $[`cat /proc/cpuinfo | grep processor | wc -l` / 2]'</script>
        <type>2</type>
        <description>
            <en>The maximum number of reduce tasks that will be run
  simultaneously by a task tracker.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.jobtracker.completeuserjobs.maximum</name>
        <value>100</value>
        <valuetype>Integer</valuetype>
        <group>job</group>
        <definition>
            <en>maximum number of complete jobs to keep around per user</en>
        </definition>
        <description>
            <en>The maximum number of complete jobs per user to keep around
  before delegating them to the job history.</en>
        </description>
    </property>
    <property>
        <name>mapreduce.reduce.input.limit</name>
        <value>-1</value>
        <valuetype>Integer</valuetype>
        <group>reduce</group>
        <definition>
            <en>The limit on the input size of the reduce</en>
        </definition>
        <description>
            <en>The limit on the input size of the reduce. If the estimated
  input size of the reduce is greater than this value, job is failed. A
  value of -1 means that there is no limit set. </en>
        </description>
    </property>
    <property>
        <name>mapred.job.tracker.retiredjobs.cache.size</name>
        <value>1000</value>
        <valuetype>Integer</valuetype>
        <group>job</group>
        <definition>
            <en>The number of retired job status to keep in the cache.</en>
        </definition>
        <description>
            <en>The number of retired job status to keep in the cache.</en>
        </description>
    </property>
    <property>
        <name>mapred.job.tracker.jobhistory.lru.cache.size</name>
        <value>5</value>
        <valuetype>Integer</valuetype>
        <group>job</group>
        <definition>
            <en>The number of job history files loaded in memory</en>
        </definition>
        <description>
            <en>The number of job history files loaded in memory. The jobs are
  loaded when they are first accessed. The cache is cleared based on LRU.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.jobtracker.instrumentation</name>
        <enable>false</enable>
        <value>org.apache.hadoop.mapred.JobTrackerMetricsSource</value>
        <valuetype>Class</valuetype>
        <group>jobtracker</group>
        <definition>
            <en>JobTracker instrumentation class</en>
        </definition>
        <description>
            <en>Expert: The instrumentation class to associate with each JobTracker.</en>
        </description>
    </property>
    <property>
        <name>mapred.child.java.opts</name>
        <value>-Xmx200m</value>
        <recommendation>-Xmx512m -XX:+UseConcMarkSweepGC -XX:ParallelCMSThreads=1 -XX:ParallelGCThreads=1</recommendation>
        <allowempty>true</allowempty>
        <valuetype>String</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>Java opts for the task tracker child processes</en>
        </definition>
        <description>
            <en>Java opts for the task tracker child processes.
  The following symbol, if present, will be interpolated: @taskid@ is replaced
  by current TaskID. Any other occurrences of '@' will go unchanged.
  For example, to enable verbose gc logging to a file named for the taskid in
  /tmp and to set the heap maximum to be a gigabyte, pass a 'value' of:
        -Xmx1024m -verbose:gc -Xloggc:/tmp/@taskid@.gc
  The configuration variable mapred.child.ulimit can be used to control the
  maximum virtual memory of the child processes.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.child.heapsize</name>
        <value>200</value>
        <valuetype>Integer</valuetype>
        <group>basic</group>
        <definition>
            <en>The JVM heapsize used by each map task and reduce task.</en>
        </definition>
        <hide>true</hide>
        <reserved>true</reserved>
        <description>
            <en>The JVM heapsize used by each map task and reduce task.</en>
        </description>
    </property>
    <property>
        <name>mapred.child.env</name>
        <value></value>
        <allowempty>true</allowempty>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>tasktracker child process environment variable</en>
        </definition>
        <description>
            <en>User added environment variables for the task tracker child
  processes. Example :
  1) A=foo  This will set the env variable A to foo
  2) B=$B:c This is inherit tasktracker's B env variable.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.child.ulimit</name>
        <value></value>
        <allowempty>true</allowempty>
<!-- The type is changed from Integer to String, as we want to support old config value like ulimited, it will treated as -1 in server -->
        <valuetype>String</valuetype>
        <group>basic</group>
        <definition>
            <en>MapReduce maximum virtual memory</en>
        </definition>
        <description>
            <en>The maximum virtual memory, in KB, of a process launched by the
  Map-Reduce framework. This can be used to control both the Mapper/Reducer
  tasks and applications using Hadoop Pipes, Hadoop Streaming etc.
  By default it is left unspecified to let cluster admins control it via
  limits.conf and other such relevant mechanisms.
  Note: mapred.child.ulimit must be greater than or equal to the -Xmx passed to
  JavaVM, else the VM might not start.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.cluster.map.memory.mb</name>
        <value>-1</value>
        <valuetype>Integer</valuetype>
        <group>map</group>
        <definition>
            <en>map virtual memory size</en>
        </definition>
        <description>
            <en>The size, in terms of virtual memory, of a single map slot
  in the Map-Reduce framework, used by the scheduler.
  A job can ask for multiple slots for a single map task via
  mapred.job.map.memory.mb, upto the limit specified by
  mapred.cluster.max.map.memory.mb, if the scheduler supports the feature.
  The value of -1 indicates that this feature is turned off.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.cluster.reduce.memory.mb</name>
        <value>-1</value>
        <valuetype>Integer</valuetype>
        <group>reduce</group>
        <definition>
            <en>reduce virtual memory size</en>
        </definition>
        <description>
            <en>The size, in terms of virtual memory, of a single reduce slot
  in the Map-Reduce framework, used by the scheduler.
  A job can ask for multiple slots for a single reduce task via
  mapred.job.reduce.memory.mb, upto the limit specified by
  mapred.cluster.max.reduce.memory.mb, if the scheduler supports the feature.
  The value of -1 indicates that this feature is turned off.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.cluster.max.map.memory.mb</name>
        <value>-1</value>
        <valuetype>Integer</valuetype>
        <group>map</group>
        <definition>
            <en>map maximum virtual memory size</en>
        </definition>
        <description>
            <en>The maximum size, in terms of virtual memory, of a single map
  task launched by the Map-Reduce framework, used by the scheduler.
  A job can ask for multiple slots for a single map task via
  mapred.job.map.memory.mb, upto the limit specified by
  mapred.cluster.max.map.memory.mb, if the scheduler supports the feature.
  The value of -1 indicates that this feature is turned off.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.cluster.max.reduce.memory.mb</name>
        <value>-1</value>
        <valuetype>Integer</valuetype>
        <group>reduce</group>
        <definition>
            <en>reduce maximum virtual memory size</en>
        </definition>
        <description>
            <en>The maximum size, in terms of virtual memory, of a single reduce
  task launched by the Map-Reduce framework, used by the scheduler.
  A job can ask for multiple slots for a single reduce task via
  mapred.job.reduce.memory.mb, upto the limit specified by
  mapred.cluster.max.reduce.memory.mb, if the scheduler supports the feature.
  The value of -1 indicates that this feature is turned off.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.job.map.memory.mb</name>
        <value>-1</value>
        <valuetype>Integer</valuetype>
        <group>map</group>
        <definition>
            <en>map virtual memory size</en>
        </definition>
        <description>
            <en>The size, in terms of virtual memory, of a single map task
  for the job.
  A job can ask for multiple slots for a single map task, rounded up to the
  next multiple of mapred.cluster.map.memory.mb and upto the limit
  specified by mapred.cluster.max.map.memory.mb, if the scheduler supports
  the feature.
  The value of -1 indicates that this feature is turned off iff
  mapred.cluster.map.memory.mb is also turned off (-1).
  </en>
        </description>
    </property>
    <property>
        <name>mapred.job.reduce.memory.mb</name>
        <value>-1</value>
        <valuetype>Integer</valuetype>
        <group>reduce</group>
        <definition>
            <en>reduce virtual memory size</en>
        </definition>
        <description>
            <en>The size, in terms of virtual memory, of a single reduce task
  for the job.
  A job can ask for multiple slots for a single map task, rounded up to the
  next multiple of mapred.cluster.reduce.memory.mb and upto the limit
  specified by mapred.cluster.max.reduce.memory.mb, if the scheduler supports
  the feature.
  The value of -1 indicates that this feature is turned off iff
  mapred.cluster.reduce.memory.mb is also turned off (-1).
  </en>
        </description>
    </property>
    <property>
        <name>mapred.child.tmp</name>
        <value>./tmp</value>
        <valuetype>String</valuetype>
        <group>basic</group>
        <definition>
            <en>tmp directory for map and reduce tasks</en>
        </definition>
        <description>
            <en> To set the value of tmp directory for map and reduce tasks.
  If the value is an absolute path, it is directly assigned. Otherwise, it is
  prepended with task's working directory. The java tasks are executed with
  option -Djava.io.tmpdir='the absolute path of the tmp dir'. Pipes and
  streaming are set with environment variable,
   TMPDIR='the absolute path of the tmp dir'
  </en>
        </description>
    </property>
    <property>
        <name>mapred.inmem.merge.threshold</name>
        <value>1000</value>
        <valuetype>Integer</valuetype>
        <group>perf</group>
        <definition>
            <en>in-memory merge threshold</en>
        </definition>
        <description>
            <en>The threshold, in terms of the number of files
  for the in-memory merge process. When we accumulate threshold number of files
  we initiate the in-memory merge and spill to disk. A value of 0 or less than
  0 indicates we want to DON'T have any threshold and instead depend only on
  the ramfs's memory consumption to trigger the merge.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.job.shuffle.merge.percent</name>
        <value>0.66</value>
        <valuetype>Float</valuetype>
        <group>perf</group>
        <definition>
            <en>The usage threshold at which an in-memory merge will be
  initiated</en>
        </definition>
        <description>
            <en>The usage threshold at which an in-memory merge will be
  initiated, expressed as a percentage of the total memory allocated to
  storing in-memory map outputs, as defined by
  mapred.job.shuffle.input.buffer.percent.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.job.shuffle.input.buffer.percent</name>
        <value>0.70</value>
        <valuetype>Float</valuetype>
        <group>perf</group>
        <definition>
            <en>memory to store map outputs during the shuffle</en>
        </definition>
        <description>
            <en>The percentage of memory to be allocated from the maximum heap
  size to storing map outputs during the shuffle.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.job.reduce.input.buffer.percent</name>
        <value>0.0</value>
        <valuetype>Float</valuetype>
        <group>perf</group>
        <definition>
            <en>The percentage of memory- relative to the maximum heap size- to
  retain map outputs during the reduce</en>
        </definition>
        <description>
            <en>The percentage of memory- relative to the maximum heap size- to
  retain map outputs during the reduce. When the shuffle is concluded, any
  remaining map outputs in memory must consume less than this threshold before
  the reduce can begin.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.map.tasks.speculative.execution</name>
        <value>true</value>
        <intel_default>true</intel_default>
        <valuetype>Boolean</valuetype>
        <group>map</group>
        <definition>
            <en>whether to execute multiple instances of map task in parallel</en>
        </definition>
        <description>
            <en>If true, then multiple instances of some map tasks
               may be executed in parallel.</en>
        </description>
    </property>
    <property>
        <name>mapred.reduce.tasks.speculative.execution</name>
        <value>true</value>
        <intel_default>true</intel_default>
                <recommendation>false</recommendation>
        <valuetype>Boolean</valuetype>
        <group>reduce</group>
        <definition>
            <en>whether to execute multiple instances of reduce task in parallel</en>
        </definition>
        <description>
            <en>If true, then multiple instances of some reduce tasks
               may be executed in parallel.</en>
        </description>
    </property>
    <property>
        <name>mapred.job.reuse.jvm.num.tasks</name>
        <value>1</value>
        <valuetype>Integer</valuetype>
        <group>perf</group>
        <definition>
            <en>Number of taks to run per jvm</en>
        </definition>
        <description>
            <en>How many tasks to run per jvm. If set to -1, there is
  no limit.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.min.split.size</name>
        <value>0</value>
        <valuetype>Integer</valuetype>
        <group>map</group>
        <definition>
            <en>The minimum size chunk that map input should be split
  into</en>
        </definition>
        <description>
            <en>The minimum size chunk that map input should be split
  into.  Note that some file formats may have minimum split sizes that
  take priority over this setting.</en>
        </description>
    </property>
    <property>
        <name>mapred.jobtracker.maxtasks.per.job</name>
        <value>-1</value>
        <valuetype>Integer</valuetype>
        <group>job</group>
        <definition>
            <en>The maximum number of tasks for a single job</en>
        </definition>
        <description>
            <en>The maximum number of tasks for a single job.
  A value of -1 indicates that there is no maximum.  </en>
        </description>
    </property>
    <property>
        <name>mapred.submit.replication</name>
        <value>10</value>
        <valuetype>Integer</valuetype>
        <group>job</group>
        <definition>
            <en>The replication level for submitted job files</en>
        </definition>
        <description>
            <en>The replication level for submitted job files.  This
  should be around the square root of the number of nodes.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.tasktracker.dns.interface</name>
        <value>default</value>
        <valuetype>String</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>The name of the Network Interface from which a task
  tracker should report its IP address</en>
        </definition>
        <description>
            <en>The name of the Network Interface from which a task
  tracker should report its IP address.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.tasktracker.dns.nameserver</name>
        <value>default</value>
        <valuetype>String</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>TaskTracker name server address</en>
        </definition>
        <description>
            <en>The host name or IP address of the name server (DNS)
  which a TaskTracker should use to determine the host name used by
  the JobTracker for communication and display purposes.
  </en>
        </description>
    </property>
    <property>
        <name>tasktracker.http.threads</name>
        <value>40</value>
        <intel_default>40</intel_default>
        <recommendation>60</recommendation>
        <valuetype>Integer</valuetype>
        <group>perf</group>
        <definition>
            <en>The number of worker threads that for the http server</en>
        </definition>
        <description>
            <en>The number of worker threads that for the http server. This is
               used for map output fetching
  </en>
        </description>
    </property>
    <property>
        <name>mapred.task.tracker.http.address</name>
        <value>0.0.0.0:50060</value>
        <valuetype>String</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>The task tracker http server address and port</en>
        </definition>
        <description>
            <en>
    The task tracker http server address and port.
    If the port is 0 then the server will start on a free port.
  </en>
        </description>
    </property>
    <property>
        <name>keep.failed.task.files</name>
        <value>false</value>
        <valuetype>Boolean</valuetype>
        <group>basic</group>
        <definition>
            <en>Whether to keep files for failed tasks</en>
        </definition>
        <description>
            <en>Should the files for failed tasks be kept. This should only be
               used on jobs that are failing, because the storage is never
               reclaimed. It also prevents the map outputs from being erased
               from the reduce directory as they are consumed.</en>
        </description>
    </property>
    <!-- <property> <name>keep.task.files.pattern</name> <value>.*_m_123456_0</value><valuetype>Integer</valuetype>
 <en></en></definition>
 <en>Keep all files from tasks whose task names match
        the given regular expression. Defaults to none.</en></description> </property> -->
    <property>
        <name>mapred.output.compress</name>
        <value>false</value>
        <valuetype>Boolean</valuetype>
        <group>job</group>
        <definition>
            <en>Whether to compress job output</en>
        </definition>
        <description>
            <en>Should the job outputs be compressed?
  </en>
        </description>
    </property>
    <property>
        <name>mapred.output.compression.type</name>
        <value>RECORD</value>
        <intel_default>RECORD</intel_default>
        <recommendation>BLOCK</recommendation>
        <valuetype>String</valuetype>
        <group>job</group>
        <definition>
            <en>compress type of job outputs</en>
        </definition>
        <description>
            <en>If the job outputs are to compressed as SequenceFiles, how should
               they be compressed? Should be one of NONE, RECORD or BLOCK.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.output.compression.codec</name>
        <value>org.apache.hadoop.io.compress.DefaultCodec</value>
        <valuetype>Class</valuetype>
        <group>job</group>
        <definition>
            <en>job outputs compress codec class</en>
        </definition>
        <description>
            <en>If the job outputs are compressed, how should they be compressed?
  </en>
        </description>
    </property>
    <property>
        <name>mapred.compress.map.output</name>
        <value>false</value>
        <intel_default>false</intel_default>
                <recommendation>true</recommendation>
        <valuetype>Boolean</valuetype>
        <group>map</group>
        <definition>
            <en>Whether to compress map outputs</en>
        </definition>
        <description>
            <en>Should the outputs of the maps be compressed before being
               sent across the network. Uses SequenceFile compression.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.map.output.compression.codec</name>
        <value>org.apache.hadoop.io.compress.DefaultCodec</value>
        <intel_default>org.apache.hadoop.io.compress.DefaultCodec</intel_default>
                <recommendation>org.apache.hadoop.io.compress.SnappyCodec</recommendation>
        <valuetype>Class</valuetype>
        <group>map</group>
        <definition>
            <en>map outputs compression class</en>
        </definition>
        <description>
            <en>If the map outputs are compressed, how should they be
               compressed?
  </en>
        </description>
    </property>
    <property>
        <name>map.sort.class</name>
        <value>org.apache.hadoop.util.QuickSort</value>
        <valuetype>Class</valuetype>
        <group>basic</group>
        <definition>
            <en>The default sort class for sorting keys.</en>
        </definition>
        <description>
            <en>The default sort class for sorting keys.</en>
        </description>
    </property>
    <property>
        <name>mapred.userlog.limit.kb</name>
        <value>0</value>
        <valuetype>Integer</valuetype>
        <group>user</group>
        <definition>
            <en>The maximum size of user-logs of each task in KB</en>
        </definition>
        <description>
            <en>The maximum size of user-logs of each task in KB. 0 disables the cap.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.userlog.retain.hours</name>
        <value>24</value>
        <valuetype>Integer</valuetype>
        <group>user</group>
        <definition>
            <en>user log maximum retain hours</en>
        </definition>
        <description>
            <en>The maximum time, in hours, for which the user-logs are to be
               retained after the job completion.</en>
        </description>
    </property>
    <property>
        <name>mapred.user.jobconf.limit</name>
        <value>5242880</value>
        <valuetype>Integer</valuetype>
        <group>user</group>
        <definition>
            <en>The maximum allowed size of the user jobconf</en>
        </definition>
        <description>
            <en>The maximum allowed size of the user jobconf. The
  default is set to 5 MB</en>
        </description>
    </property>
    <property>
        <name>mapred.hosts</name>
        <value></value>
        <allowempty>true</allowempty>
        <valuetype>Integer</valuetype>
        <group>jobtracker</group>
        <definition>
            <en>Names a file that contains the list of nodes that may
  connect to the jobtracker.</en>
        </definition>
        <description>
            <en>Names a file that contains the list of nodes that may
  connect to the jobtracker.  If the value is empty, all hosts are
  permitted.</en>
        </description>
    </property>
    <property>
        <name>mapred.hosts.exclude</name>
        <value></value>
        <allowempty>true</allowempty>
        <valuetype>String</valuetype>
        <group>jobtracker</group>
        <definition>
            <en>Names a file that contains the list of hosts that
  should be excluded by the jobtracker</en>
        </definition>
        <description>
            <en>Names a file that contains the list of hosts that
  should be excluded by the jobtracker.  If the value is empty, no
  hosts are excluded.</en>
        </description>
    </property>
    <property>
        <name>mapred.heartbeats.in.second</name>
        <value>100</value>
        <valuetype>Integer</valuetype>
        <group>jobtracker</group>
        <definition>
            <en>Approximate number of heart-beats that could arrive
               at JobTracker in a second</en>
        </definition>
        <description>
            <en>Expert: Approximate number of heart-beats that could arrive
               at JobTracker in a second. Assuming each RPC can be processed
               in 10msec, the default value is made 100 RPCs in a second.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.max.tracker.blacklists</name>
        <value>4</value>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>TaskTracker maximum number of blacklists</en>
        </definition>
        <description>
            <en>The number of blacklists for a tasktracker by various jobs
               after which the tasktracker will be marked as potentially
               faulty and is a candidate for graylisting across all jobs.
               (Unlike blacklisting, this is advisory; the tracker remains
               active.  However, it is reported as graylisted in the web UI,
               with the expectation that chronically graylisted trackers
               will be manually decommissioned.)  This value is tied to
               mapred.jobtracker.blacklist.fault-timeout-window; faults
               older than the window width are forgiven, so the tracker
               will recover from transient problems.  It will also become
               healthy after a restart.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.jobtracker.blacklist.fault-timeout-window</name>
        <value>180</value>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>The timeout (in minutes) after which per-job tasktracker
               faults are forgiven</en>
        </definition>
        <description>
            <en>The timeout (in minutes) after which per-job tasktracker
               faults are forgiven.  The window is logically a circular
               buffer of time-interval buckets whose width is defined by
               mapred.jobtracker.blacklist.fault-bucket-width; when the
               "now" pointer moves across a bucket boundary, the previous
               contents (faults) of the new bucket are cleared.  In other
               words, the timeout's granularity is determined by the bucket
               width.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.jobtracker.blacklist.fault-bucket-width</name>
        <value>15</value>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>TaskTracker fault timeout window bucket width</en>
        </definition>
        <description>
            <en>The width (in minutes) of each bucket in the tasktracker
               fault timeout window.  Each bucket is reused in a circular
               manner after a full timeout-window interval (defined by
               mapred.jobtracker.blacklist.fault-timeout-window).
  </en>
        </description>
    </property>
    <property>
        <name>mapred.max.tracker.failures</name>
        <value>4</value>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>TaskTracker maximum failures</en>
        </definition>
        <description>
            <en>The number of task-failures on a tasktracker of a given job
               after which new tasks of that job aren't assigned to it.
  </en>
        </description>
    </property>
    <property>
        <name>jobclient.output.filter</name>
        <value>FAILED</value>
        <valuetype>String</valuetype>
        <group>user</group>
        <definition>
            <en>he filter for controlling the output of the task's userlogs sent
               to the console of the JobClient</en>
        </definition>
        <description>
            <en>The filter for controlling the output of the task's userlogs sent
               to the console of the JobClient.
               The permissible options are: NONE, KILLED, FAILED, SUCCEEDED and
               ALL.
  </en>
        </description>
    </property>
    <property>
        <name>jobclient.completion.poll.interval</name>
        <value>5000</value>
        <valuetype>Integer</valuetype>
        <group>user</group>
        <definition>
            <en>JobClient polling JobTracker interval</en>
        </definition>
        <description>
            <en>The interval (in milliseconds) between which the JobClient
    polls the JobTracker for updates about job status. You may want to set this
    to a lower value to make tests run faster on a single node system. Adjusting
    this value in production may lead to unwanted client-server traffic.
    </en>
        </description>
    </property>
    <property>
        <name>jobclient.progress.monitor.poll.interval</name>
        <value>1000</value>
        <valuetype>Integer</valuetype>
        <group>user</group>
        <definition>
            <en>The interval (in milliseconds) between which the JobClient
    reports status to the console and checks for job completion</en>
        </definition>
        <description>
            <en>The interval (in milliseconds) between which the JobClient
    reports status to the console and checks for job completion. You may want to set this
    to a lower value to make tests run faster on a single node system. Adjusting
    this value in production may lead to unwanted client-server traffic.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.job.tracker.persist.jobstatus.active</name>
        <value>false</value>
        <valuetype>Boolean</valuetype>
        <group>job</group>
        <definition>
            <en>Indicates if persistency of job status information is
      active or not.</en>
        </definition>
        <description>
            <en>Indicates if persistency of job status information is
      active or not.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.job.tracker.persist.jobstatus.hours</name>
        <value>0</value>
        <valuetype>Integer</valuetype>
        <group>job</group>
        <definition>
            <en>he number of hours job status information is persisted in DFS.</en>
        </definition>
        <description>
            <en>The number of hours job status information is persisted in DFS.
    The job status information will be available after it drops of the memory
    queue and between jobtracker restarts. With a zero value the job status
    information is not persisted at all in DFS.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.job.tracker.persist.jobstatus.dir</name>
        <value>/jobtracker/jobsInfo</value>
        <valuetype>Directory</valuetype>
        <group>job</group>
        <definition>
            <en>The directory where the job status information is persisted</en>
        </definition>
        <description>
            <en>The directory where the job status information is persisted
      in a file system to be available after it drops of the memory queue and
      between jobtracker restarts.
    </en>
        </description>
    </property>
    <property>
        <name>mapreduce.job.complete.cancel.delegation.tokens</name>
        <value>true</value>
        <valuetype>Boolean</valuetype>
        <group>job</group>
        <definition>
            <en>Whether to unregister delegation tokens from renewal</en>
        </definition>
        <description>
            <en> if false - do not unregister/cancel delegation tokens
    from renewal, because same tokens may be used by spawned jobs
    </en>
        </description>
    </property>
    <property>
        <name>mapred.task.profile</name>
        <value>false</value>
        <valuetype>Boolean</valuetype>
        <group>basic</group>
        <definition>
            <en>Whether to collect profiler information</en>
        </definition>
        <description>
            <en>To set whether the system should collect profiler
     information for some of the tasks in this job? The information is stored
     in the user log directory. The value is "true" if task profiling
     is enabled.</en>
        </description>
    </property>
    <property>
        <name>mapred.task.profile.maps</name>
        <value>0-2</value>
        <valuetype>Int_range</valuetype>
        <group>map</group>
        <definition>
            <en>ranges of map tasks to profile</en>
        </definition>
        <description>
            <en> To set the ranges of map tasks to profile.
    mapred.task.profile has to be set to true for the value to be accounted.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.task.profile.reduces</name>
        <value>0-2</value>
        <valuetype>Int_range</valuetype>
        <group>reduce</group>
        <definition>
            <en>ranges of reduce tasks to profile</en>
        </definition>
        <description>
            <en> To set the ranges of reduce tasks to profile.
    mapred.task.profile has to be set to true for the value to be accounted.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.line.input.format.linespermap</name>
        <value>1</value>
        <valuetype>Integer</valuetype>
        <group>basic</group>
        <definition>
            <en>Number of lines per split in NLineInputFormat</en>
        </definition>
        <description>
            <en> Number of lines per split in NLineInputFormat.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.skip.attempts.to.start.skipping</name>
        <value>2</value>
        <valuetype>Integer</valuetype>
        <group>skip</group>
        <definition>
            <en>he number of Task attempts AFTER which skip mode
    will be kicked off</en>
        </definition>
        <description>
            <en> The number of Task attempts AFTER which skip mode
    will be kicked off. When skip mode is kicked off, the
    tasks reports the range of records which it will process
    next, to the TaskTracker. So that on failures, TT knows which
    ones are possibly the bad records. On further executions,
    those are skipped.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.skip.map.auto.incr.proc.count</name>
        <value>true</value>
        <valuetype>Boolean</valuetype>
        <group>skip</group>
        <definition>
            <en>Whether to increment SkipBadRecords.COUNTER_MAP_PROCESSED_GROUPS</en>
        </definition>
        <description>
            <en> The flag which if set to true,
    SkipBadRecords.COUNTER_MAP_PROCESSED_RECORDS is incremented
    by MapRunner after invoking the map function. This value must be set to
    false for applications which process the records asynchronously
    or buffer the input records. For example streaming.
    In such cases applications should increment this counter on their own.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.skip.reduce.auto.incr.proc.count</name>
        <value>true</value>
        <valuetype>Boolean</valuetype>
        <group>skip</group>
        <definition>
            <en>Whether to increment SkipBadRecords.COUNTER_REDUCE_PROCESSED_GROUPS</en>
        </definition>
        <description>
            <en> The flag which if set to true,
    SkipBadRecords.COUNTER_REDUCE_PROCESSED_GROUPS is incremented
    by framework after invoking the reduce function. This value must be set to
    false for applications which process the records asynchronously
    or buffer the input records. For example streaming.
    In such cases applications should increment this counter on their own.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.skip.out.dir</name>
        <value></value>
        <allowempty>true</allowempty>
        <valuetype>String</valuetype>
        <group>skip</group>
        <definition>
            <en>skipped records output directory</en>
        </definition>
        <description>
            <en> If no value is specified here, the skipped records are
    written to the output directory at _logs/skip.
    User can stop writing skipped records by giving the value "none".
    </en>
        </description>
    </property>
    <property>
        <name>mapred.skip.map.max.skip.records</name>
        <value>0</value>
        <valuetype>Integer</valuetype>
        <group>skip</group>
        <definition>
            <en>The number of acceptable skip records surrounding the bad
    record PER bad record in mapper</en>
        </definition>
        <description>
            <en> The number of acceptable skip records surrounding the bad
    record PER bad record in mapper. The number includes the bad record as well.
    To turn the feature of detection/skipping of bad records off, set the
    value to 0.
    The framework tries to narrow down the skipped range by retrying
    until this threshold is met OR all attempts get exhausted for this task.
    Set the value to Long.MAX_VALUE to indicate that framework need not try to
    narrow down. Whatever records(depends on application) get skipped are
    acceptable.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.skip.reduce.max.skip.groups</name>
        <value>0</value>
        <valuetype>Integer</valuetype>
        <group>skip</group>
        <definition>
            <en>The number of acceptable skip groups surrounding the bad
    group PER bad group in reducer</en>
        </definition>
        <description>
            <en> The number of acceptable skip groups surrounding the bad
    group PER bad group in reducer. The number includes the bad group as well.
    To turn the feature of detection/skipping of bad groups off, set the
    value to 0.
    The framework tries to narrow down the skipped range by retrying
    until this threshold is met OR all attempts get exhausted for this task.
    Set the value to Long.MAX_VALUE to indicate that framework need not try to
    narrow down. Whatever groups(depends on application) get skipped are
    acceptable.
    </en>
        </description>
    </property>
    <!-- Job Notification Configuration -->
    <!-- <property> <name>job.end.notification.url</name> <value>http://localhost:8080/jobstatus.php?jobId=$jobId&amp;jobStatus=$jobStatus</value><valuetype>String</valuetype>
 <en></en></definition>
 <en>Indicates url which will be called on completion
        of job to inform end status of job. User can give at most 2 variables with
        URI : $jobId and $jobStatus. If they are present in URI, then they will be
        replaced by their respective values. </en></description> </property> -->
    <property>
        <name>job.end.retry.attempts</name>
        <value>0</value>
        <valuetype>Integer</valuetype>
        <group>basic</group>
        <definition>
            <en>hadoop retry attempts to contact notification URL</en>
        </definition>
        <description>
            <en>Indicates how many times hadoop should attempt to contact the
               notification URL </en>
        </description>
    </property>
    <property>
        <name>job.end.retry.interval</name>
        <value>30000</value>
        <valuetype>Integer</valuetype>
        <group>basic</group>
        <definition>
            <en>notifcation URL retry interval</en>
        </definition>
        <description>
            <en>Indicates time in milliseconds between notification URL retry
                calls</en>
        </description>
    </property>
    <!-- Proxy Configuration -->
    <property>
        <name>hadoop.rpc.socket.factory.class.JobSubmissionProtocol</name>
        <value></value>
        <allowempty>true</allowempty>
        <valuetype>String</valuetype>
        <group>basic</group>
        <definition>
            <en>SocketFactory to use to connect to a Map/Reduce master (JobTracker)</en>
        </definition>
        <description>
            <en>SocketFactory to use to connect to a Map/Reduce master
    (JobTracker). If null or empty, then use hadoop.rpc.socket.class.default.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.task.cache.levels</name>
        <value>2</value>
        <valuetype>Integer</valuetype>
        <group>perf</group>
        <definition>
            <en>max level of the task cache</en>
        </definition>
        <description>
            <en> This is the max level of the task cache. For example, if
    the level is 2, the tasks cached are at the host level and at the rack
    level.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.queue.names</name>
        <hide>false</hide>
        <value>default</value>
        <valuetype>String</valuetype>
        <group>jobtracker</group>
        <definition>
            <en>list of queues configured for this jobtracker</en>
        </definition>
        <description>
            <en> Comma separated list of queues configured for this jobtracker.
    Jobs are added to queues and schedulers can configure different
    scheduling properties for the various queues. To configure a property
    for a queue, the name of the queue must match the name specified in this
    value. Queue properties that are common to all schedulers are configured
    here with the naming convention, mapred.queue.$QUEUE-NAME.$PROPERTY-NAME,
    for e.g. mapred.queue.default.submit-job-acl.
    The number of queues configured in this parameter could depend on the
    type of scheduler being used, as specified in
    mapred.jobtracker.taskScheduler. For example, the JobQueueTaskScheduler
    supports only a single queue, which is the default configured here.
    Before adding more queues, ensure that the scheduler you've configured
    supports multiple queues.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.acls.enabled</name>
        <readonly>true</readonly>
        <value>false</value>
        <valuetype>Boolean</valuetype>
        <group>basic</group>
        <definition>
            <en>Whether to enable ACL check</en>
        </definition>
        <description>
            <en>Specifies whether ACLs should be checked
    for authorization of users for doing various queue and job level operations.
    ACLs are disabled by default. If enabled, access control checks are made by
    JobTracker and TaskTracker when requests are made by users for queue
    operations like submit job to a queue and kill a job in the queue and job
    operations like viewing the job-details (See mapreduce.job.acl-view-job)
    or for modifying the job (See mapreduce.job.acl-modify-job) using
    Map/Reduce APIs, RPCs or via the console and web user interfaces.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.queue.default.state</name>
        <value>RUNNING</value>
        <valuetype>String</valuetype>
        <group>basic</group>
        <definition>
            <en>job state value</en>
        </definition>
        <description>
            <en>
   This values defines the state , default queue is in.
   the values can be either "STOPPED" or "RUNNING"
   This value can be changed at runtime.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.job.queue.name</name>
        <value>default</value>
        <valuetype>String</valuetype>
        <group>job</group>
        <definition>
            <en>Queue to which a job is submitted</en>
        </definition>
        <description>
            <en> Queue to which a job is submitted. This must match one of the
    queues defined in mapred.queue.names for the system. Also, the ACL setup
    for the queue must allow the current user to submit a job to the queue.
    Before specifying a queue, ensure that the system is configured with
    the queue, and access is allowed for submitting jobs to the queue.
  </en>
        </description>
    </property>
    <property>
        <name>mapreduce.job.acl-modify-job</name>
        <value></value>
<!-- This is for compability, that old bin contains characters string with space. For AnyString, we will not do any validation -->
        <valuetype>String</valuetype>
        <allowempty>true</allowempty>
        <group>job</group>
        <definition>
            <en>Job specific access-control list for 'modifying' the job</en>
        </definition>
        <description>
            <en> Job specific access-control list for 'modifying' the job. It
    is only used if authorization is enabled in Map/Reduce by setting the
    configuration property mapred.acls.enabled to true.
    This specifies the list of users and/or groups who can do modification
    operations on the job. For specifying a list of users and groups the
    format to use is "user1,user2 group1,group". If set to '*', it allows all
    users/groups to modify this job. If set to ' '(i.e. space), it allows
    none. This configuration is used to guard all the modifications with respect
    to this job and takes care of all the following operations:
      o killing this job
      o killing a task of this job, failing a task of this job
      o setting the priority of this job
    Each of these operations are also protected by the per-queue level ACL
    "acl-administer-jobs" configured via mapred-queues.xml. So a caller should
    have the authorization to satisfy either the queue-level ACL or the
    job-level ACL.
    Irrespective of this ACL configuration, job-owner, the user who started the
    cluster, cluster administrators configured via
    mapreduce.cluster.administrators and queue administrators of the queue to
    which this job is submitted to configured via
    mapred.queue.queue-name.acl-administer-jobs  in mapred-queue-acls.xml can
    do all the modification operations on a job.
    By default, nobody else besides job-owner, the user who started the cluster,
    cluster administrators and queue administrators can perform modification
    operations on a job.
  </en>
        </description>
    </property>
    <property>
        <name>mapreduce.job.acl-view-job</name>
        <value></value>
<!-- This is for compability, that old bin contains characters string with space. For AnyString, we will not do any validation -->
        <valuetype>String</valuetype>
        <allowempty>true</allowempty>
        <group>job</group>
        <definition>
            <en>Job specific access-control list for 'viewing' the job</en>
        </definition>
        <description>
            <en> Job specific access-control list for 'viewing' the job. It is
    only used if authorization is enabled in Map/Reduce by setting the
    configuration property mapred.acls.enabled to true.
    This specifies the list of users and/or groups who can view private details
    about the job. For specifying a list of users and groups the
    format to use is "user1,user2 group1,group". If set to '*', it allows all
    users/groups to view this job. If set to ' '(i.e. space), it allows
    none. This configuration is used to guard some of the job-views and at
    present only protects APIs that can return possibly sensitive information
    of the job-owner like
      o job-level counters
      o task-level counters
      o tasks' diagnostic information
      o task-logs displayed on the TaskTracker web-UI and
      o job.xml showed by the JobTracker's web-UI
    Every other piece of information of jobs is still accessible by any other
    user, for e.g., JobStatus, JobProfile, list of jobs in the queue, etc.
    Irrespective of this ACL configuration, job-owner, the user who started the
    cluster, cluster administrators configured via
    mapreduce.cluster.administrators and queue administrators of the queue to
    which this job is submitted to configured via
    mapred.queue.queue-name.acl-administer-jobs in mapred-queue-acls.xml can do
    all the view operations on a job.
    By default, nobody else besides job-owner, the user who started the
    cluster, cluster administrators and queue administrators can perform
    view operations on a job.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.tasktracker.indexcache.mb</name>
        <value>10</value>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>The maximum memory that a task tracker allows for the index cache </en>
        </definition>
        <description>
            <en> The maximum memory that a task tracker allows for the
    index cache that is used when serving map outputs to reducers.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.combine.recordsBeforeProgress</name>
        <value>10000</value>
        <valuetype>Integer</valuetype>
        <group>basic</group>
        <definition>
            <en> The number of records to process during combine output collection
   before sending a progress notification to the TaskTracker.</en>
        </definition>
        <description>
            <en> The number of records to process during combine output collection
   before sending a progress notification to the TaskTracker.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.merge.recordsBeforeProgress</name>
        <value>10000</value>
        <valuetype>Integer</valuetype>
        <group>basic</group>
        <definition>
            <en> The number of records to process during merge before
   sending a progress notification to the TaskTracker.</en>
        </definition>
        <description>
            <en> The number of records to process during merge before
   sending a progress notification to the TaskTracker.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.reduce.slowstart.completed.maps</name>
        <value>0.05</value>
        <valuetype>Float</valuetype>
        <group>job</group>
        <definition>
            <en>Fraction of the number of maps in the job which should be
  complete before reduces are scheduled for the job</en>
        </definition>
        <description>
            <en>Fraction of the number of maps in the job which should be
  complete before reduces are scheduled for the job.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.task.tracker.task-controller</name>
        <value>org.apache.hadoop.mapred.DefaultTaskController</value>
        <valuetype>Class</valuetype>
        <group>basic</group>
        <definition>
            <en>TaskController which is used to launch and manage task execution </en>
        </definition>
        <description>
            <en>TaskController which is used to launch and manage task execution </en>
        </description>
    </property>
    <property>
        <name>mapreduce.tasktracker.group</name>
        <value></value>
        <allowempty>true</allowempty>
        <valuetype>String</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>Group to which TaskTracker belongs</en>
        </definition>
        <description>
            <en>Expert: Group to which TaskTracker belongs. If
   LinuxTaskController is configured via mapreduce.tasktracker.taskcontroller,
   the group owner of the task-controller binary should be same as this group.
  </en>
        </description>
    </property>
    <property>
        <name>mapred.disk.healthChecker.interval</name>
        <value>60000</value>
        <valuetype>Integer</valuetype>
        <group>health</group>
        <definition>
            <en>node health check interval</en>
        </definition>
        <description>
            <en>How often the TaskTracker checks the health of its
 local directories. Configuring this to a value smaller than the
 heartbeat interval is equivalent to setting this to heartbeat
 interval value.
 </en>
        </description>
    </property>
    <!-- Node health script variables -->
    <property>
        <name>mapred.healthChecker.script.path</name>
        <value></value>
        <allowempty>true</allowempty>
        <valuetype>Integer</valuetype>
        <group>health</group>
        <definition>
            <en>node health script path</en>
        </definition>
        <description>
            <en>Absolute path to the script which is
  periodically run by the node health monitoring service to determine if
  the node is healthy or not. If the value of this key is empty or the
  file does not exist in the location configured here, the node health
  monitoring service is not started.</en>
        </description>
    </property>
    <property>
        <name>mapred.healthChecker.interval</name>
        <value>60000</value>
        <valuetype>Integer</valuetype>
        <group>health</group>
        <definition>
            <en>Frequency of the node health script to be run </en>
        </definition>
        <description>
            <en>Frequency of the node health script to be run </en>
        </description>
    </property>
    <property>
        <name>mapred.healthChecker.script.timeout</name>
        <value>600000</value>
        <valuetype>Integer</valuetype>
        <group>health</group>
        <definition>
            <en>node health script timeout</en>
        </definition>
        <description>
            <en>Time after node health script should be killed if
  unresponsive and considered that the script has failed.</en>
        </description>
    </property>
    <property>
        <name>mapred.healthChecker.script.args</name>
        <value></value>
        <allowempty>true</allowempty>
        <valuetype>String</valuetype>
        <group>health</group>
        <definition>
            <en>List of arguments which are to be passed to
  node health script when it is being launched comma seperated.</en>
        </definition>
        <description>
            <en>List of arguments which are to be passed to
  node health script when it is being launched comma seperated.
  </en>
        </description>
    </property>
    <property>
        <name>mapreduce.job.counters.limit</name>
        <value>120</value>
        <valuetype>Integer</valuetype>
        <group>job</group>
        <definition>
            <en>Limit on the number of counters allowed per job.</en>
        </definition>
        <description>
            <en>Limit on the number of counters allowed per job.</en>
        </description>
    </property>
    <property>
        <name>mapreduce.slot.memory.weight</name>
        <value></value>
        <recommendation>50</recommendation>
        <valuetype>Integer</valuetype>
        <group>tasktracker</group>
        <definition>
            <en>TaskTracker reserve heapsize weight</en>
        </definition>
    <global>true</global>
        <sectionname>directory</sectionname>
        <description>
            <en>The weight of tasktracker reserve heapsize and the default value is 50.</en>
        </description>
        <form>TextItem</form>
    </property>
    <!-- end of node health script variables -->
    <property>
        <name>mapred.scheduler</name>
        <value>fair</value>
        <valuetype>String</valuetype>
        <group>basic</group>
        <definition>
            <en>Task Schedule</en>
        </definition>
        <reserved>true</reserved>
        <sectionname>advanced</sectionname>
        <description>
            <en>Map/Reduce Task schedule method. If the Capacity scheduler has been selected, then additional items need to be configured.</en>
        </description>
        <form>RadioGroupItem</form>
        <radios>fair,capacity</radios>
    </property>
    <property>
        <name>mapred.map.reduce.ratio</name>
        <value>2</value>
        <valuetype>Integer</valuetype>
        <group>basic</group>
        <definition>
            <en>The map/reduce ratio.</en>
        </definition>
        <reserved>true</reserved>
        <description>
            <en>The map/reduce ratio.</en>
        </description>
    </property>
    <property>
        <name>mapred.cpu.ratio.max</name>
        <value>1.5</value>
        <valuetype>Float</valuetype>
        <group>basic</group>
        <definition>
            <en>The cpu max usage ratio.</en>
        </definition>
        <reserved>true</reserved>
        <description>
            <en>The cpu max usage ratio.</en>
        </description>
    </property>
    <!-- no description available -->
    <property>
        <name>mapred.fairscheduler.preemption</name>
        <enable>false</enable>
        <value>true</value>
        <valuetype>Boolean</valuetype>
        <group>perf</group>
        <definition>
            <en>Whether to enable fairscheduler preemption.</en>
        </definition>
        <description>
            <en>Whether to enable fairscheduler preemption.</en>
        </description>
    </property>
    <property>
        <name>mapred.fairscheduler.assignmultiple</name>
        <enable>false</enable>
        <value>true</value>
        <valuetype>Boolean</valuetype>
        <group>perf</group>
        <definition>
            <en>Whether to assign multiple</en>
        </definition>
        <description>
            <en>Whether to assign multiple</en>
        </description>
    </property>
    <property>
        <name>mapred.fairscheduler.sizebasedweight</name>
        <enable>false</enable>
        <value>true</value>
        <valuetype>Boolean</valuetype>
        <group>perf</group>
        <definition>
            <en>size based weight</en>
        </definition>
        <description>
            <en>size based weight</en>
        </description>
    </property>
    <property>
        <name>mapred.fairscheduler.poolnameproperty</name>
        <enable>false</enable>
        <value>mapred.queue.name</value>
        <valuetype>String</valuetype>
        <group>perf</group>
        <definition>
            <en>pool name property</en>
        </definition>
        <description>
            <en>job.set("mapred.queue.name",pool); // pool is set to either 'high' or 'low' </en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.maximum-system-jobs</name>
        <value>3000</value>
        <valuetype>Integer</valuetype>
        <group>basic</group>
        <definition>
            <en>Maximum number of jobs in the system which can be initialized,
     concurrently, by the CapacityScheduler</en>
        </definition>
        <description>
            <en>Maximum number of jobs in the system which can be initialized,
     concurrently, by the CapacityScheduler.</en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.queue.default.capacity</name>
        <value>100</value>
        <valuetype>Integer</valuetype>
        <group>basic</group>
        <definition>
            <en>Percentage of the number of slots in the cluster that are
      to be available for jobs in this queue.</en>
        </definition>
        <description>
            <en>Percentage of the number of slots in the cluster that are
      to be available for jobs in this queue.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.queue.default.maximum-capacity</name>
        <value>-1</value>
        <valuetype>Integer</valuetype>
        <group>scheduling</group>
        <definition>
            <en>per-queue maximum-capacity</en>
        </definition>
        <description>
            <en>
    maximum-capacity defines a limit beyond which a queue cannot use the capacity of the cluster.
    This provides a means to limit how much excess capacity a queue can use. By default, there is no limit.
    The maximum-capacity of a queue can only be greater than or equal to its minimum capacity.
        Default value of -1 implies a queue can use complete capacity of the cluster.
        This property could be to curtail certain jobs which are long running in nature from occupying more than a
        certain percentage of the cluster, which in the absence of pre-emption, could lead to capacity guarantees of
        other queues being affected.
        One important thing to note is that maximum-capacity is a percentage , so based on the cluster's capacity
        the max capacity would change. So if large number of nodes or racks get added to the cluster , max Capacity in
        absolute terms would increase accordingly.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.queue.default.supports-priority</name>
        <value>false</value>
        <valuetype>Boolean</valuetype>
        <group>scheduling</group>
        <definition>
            <en>Whether to take jobs' priorities into account in scheduling decisions</en>
        </definition>
        <description>
            <en>If true, priorities of jobs will be taken into
      account in scheduling decisions.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.queue.default.minimum-user-limit-percent</name>
        <value>100</value>
        <valuetype>Integer</valuetype>
        <group>scheduling</group>
        <definition>
            <en>maximum limit on per-user's allocated percentage of resources</en>
        </definition>
        <description>
            <!-- can't understand the example -->
            <en> Each queue enforces a limit on the percentage of resources
    allocated to a user at any given time, if there is competition for them.
    This user limit can vary between a minimum and maximum value. The former
    depends on the number of users who have submitted jobs, and the latter is
    set to this property value. For example, suppose the value of this
    property is 25. If two users have submitted jobs to a queue, no single
    user can use more than 50% of the queue resources. If a third user submits
    a job, no single user can use more than 33% of the queue resources. With 4
    or more users, no user can use more than 25% of the queue's resources. A
    value of 100 implies no user limits are imposed.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.queue.default.user-limit-factor</name>
        <value>1</value>
        <valuetype>Integer</valuetype>
        <group>scheduling</group>
        <definition>
            <en>The multiple of the queue capacity which can be configured to
    allow a single user to acquire more slots.
    </en>
        </definition>
        <description>
            <en>The multiple of the queue capacity which can be configured to
    allow a single user to acquire more slots.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.queue.default.maximum-initialized-active-tasks</name>
        <value>200000</value>
        <valuetype>Integer</valuetype>
        <group>scheduling</group>
        <definition>
            <en>The maximum number of tasks, across all jobs in the queue,
    which can be initialized concurrently.</en>
        </definition>
        <description>
            <en>The maximum number of tasks, across all jobs in the queue,
    which can be initialized concurrently. Once the queue's jobs exceed this
    limit they will be queued on disk.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.queue.default.maximum-initialized-active-tasks-per-user</name>
        <value>100000</value>
        <valuetype>Integer</valuetype>
        <group>scheduling</group>
        <definition>
            <en>The maximum number of tasks per-user, across all the of the
    user's jobs in the queue, which can be initialized concurrently</en>
        </definition>
        <description>
            <en>The maximum number of tasks per-user, across all the of the
    user's jobs in the queue, which can be initialized concurrently. Once the
    user's jobs exceed this limit they will be queued on disk.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.queue.default.init-accept-jobs-factor</name>
        <value>10</value>
        <valuetype>Integer</valuetype>
        <group>scheduling</group>
        <definition>
            <en>The multipe of (maximum-system-jobs * queue-capacity) used to
    determine the number of jobs which are accepted by the scheduler.</en>
        </definition>
        <description>
            <en>The multipe of (maximum-system-jobs * queue-capacity) used to
    determine the number of jobs which are accepted by the scheduler.</en>
        </description>
    </property>
    <!-- The default configuration settings for the capacity task scheduler -->
    <!-- The default values would be applied to all the queues which don't have -->
    <!-- the appropriate property for the particular queue -->
    <property>
        <name>mapred.capacity-scheduler.default-supports-priority</name>
        <value>false</value>
        <valuetype>Boolean</valuetype>
        <group>scheduling</group>
        <definition>
            <en>If true, priorities of jobs will be taken into
      account in scheduling decisions by default in a job queue.</en>
        </definition>
        <description>
            <en>If true, priorities of jobs will be taken into
      account in scheduling decisions by default in a job queue.</en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.default-minimum-user-limit-percent</name>
        <value>100</value>
        <valuetype>Integer</valuetype>
        <group>scheduling</group>
        <definition>
            <en>The percentage of the resources limited to a particular user
      for the job queue at any given point of time by default.</en>
        </definition>
        <description>
            <en>The percentage of the resources limited to a particular user
      for the job queue at any given point of time by default.</en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.default-user-limit-factor</name>
        <value>1</value>
        <valuetype>Integer</valuetype>
        <group>scheduling</group>
        <definition>
            <en>The default multiple of queue-capacity which is used to
    determine the amount of slots a single user can consume concurrently.
    </en>
        </definition>
        <description>
            <en>The default multiple of queue-capacity which is used to
    determine the amount of slots a single user can consume concurrently.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.default-maximum-active-tasks-per-queue</name>
        <value>200000</value>
        <valuetype>Integer</valuetype>
        <group>scheduling</group>
        <definition>
            <en>The default maximum number of tasks, across all jobs in the
    queue, which can be initialized concurrently</en>
        </definition>
        <description>
            <en>The default maximum number of tasks, across all jobs in the
    queue, which can be initialized concurrently. Once the queue's jobs exceed
    this limit they will be queued on disk.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.default-maximum-active-tasks-per-user</name>
        <value>100000</value>
        <valuetype>Integer</valuetype>
        <group>scheduling</group>
        <definition>
            <en>The default maximum number of tasks per-user, across all the of
    the user's jobs in the queue, which can be initialized concurrently</en>
        </definition>
        <description>
            <en>The default maximum number of tasks per-user, across all the of
    the user's jobs in the queue, which can be initialized concurrently. Once
    the user's jobs exceed this limit they will be queued on disk.
    </en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.default-init-accept-jobs-factor</name>
        <value>10</value>
        <valuetype>Integer</valuetype>
        <group>scheduling</group>
        <definition>
            <en>The default multipe of (maximum-system-jobs * queue-capacity)
    used to determine the number of jobs which are accepted by the scheduler.
    </en>
        </definition>
        <description>
            <en>The default multipe of (maximum-system-jobs * queue-capacity)
    used to determine the number of jobs which are accepted by the scheduler.
    </en>
        </description>
    </property>
    <!-- Capacity scheduler Job Initialization configuration parameters -->
    <property>
        <name>mapred.capacity-scheduler.init-poll-interval</name>
        <value>5000</value>
        <valuetype>Integer</valuetype>
        <group>scheduling</group>
        <definition>
            <en>The amount of time in miliseconds which is used to poll
    the job queues for jobs to initialize.</en>
        </definition>
        <description>
            <en>The amount of time in miliseconds which is used to poll
    the job queues for jobs to initialize.</en>
        </description>
    </property>
    <property>
        <name>mapred.capacity-scheduler.init-worker-threads</name>
        <value>5</value>
        <valuetype>Integer</valuetype>
        <group>scheduling</group>
        <definition>
            <en>Number of worker threads which would be used by
    Initialization poller to initialize jobs in a set of queue</en>
        </definition>
        <description>
            <en>Number of worker threads which would be used by
    Initialization poller to initialize jobs in a set of queue.
    If number mentioned in property is equal to number of job queues
    then a single thread would initialize jobs in a queue. If lesser
    then a thread would get a set of queues assigned. If the number
    is greater then number of threads would be equal to number of
    job queues.
    </en>
        </description>
    </property>
    <property>
        <name>resmon.joblevel.metrics.enabled</name>
        <value>false</value>
        <valuetype>Boolean</valuetype>
        <group>basic</group>
        <definition>
            <en>Whether to enable joblevel metrics</en>
        </definition>
        <reserved>true</reserved>
        <description>
            <en>Whether to enable joblevel metrics</en>
        </description>
    </property>
    <property>
        <name>mapred.profiling</name>
        <value>false</value>
        <valuetype>Boolean</valuetype>
        <group>profiling</group>
        <definition>
            <en>Whether to enable profiling or not</en>
        </definition>
        <description>
            <en>The flag to determine whether Profiling Feature enable or not.
    </en>
        </description>
    </property>
    <briefsection>
        <sectionname>directory</sectionname>
        <name_en>Configuration</name_en>
        <autoexpand>true</autoexpand>
        <showdescription>false</showdescription>
    </briefsection>
    <briefsection>
        <sectionname>advanced</sectionname>
        <name_en>Advanced Configuration</name_en>
        <autoexpand>true</autoexpand>
        <showdescription>false</showdescription>
    </briefsection>
    <group>
        <id>basic</id>
        <name_en>Basic Configuration</name_en>
        <description_en>Basic configurations that get HDFS running.</description_en>
    </group>
    <group>
        <id>perf</id>
        <name_en>Performance</name_en>
        <description_en>Configurations that affect Hadoop's performance</description_en>
    </group>
    <group>
        <id>jobtracker</id>
        <name_en>Jobtracker Configuration</name_en>
        <description_en>Configurations for Jobtracker.</description_en>
    </group>
    <group>
        <id>tasktracker</id>
        <name_en>Tasktracker Configuration</name_en>
        <description_en>Configurations for Tasktracker.</description_en>
    </group>
    <group>
        <id>map</id>
        <name_en>Map Configuration</name_en>
        <description_en>Configurations for Map job.</description_en>
    </group>
    <group>
        <id>reduce</id>
        <name_en>Reduce Configuration</name_en>
        <description_en>Configurations for Reduce job.</description_en>
    </group>
    <group>
        <id>io</id>
        <name_en>IO Configuration</name_en>
        <description_en>Configurations for Input/Output.</description_en>
    </group>
    <group>
        <id>job</id>
        <name_en>Job Configuration</name_en>
        <description_en>Configurations for a job.</description_en>
    </group>
    <group>
        <id>user</id>
        <name_en>Configurations for user</name_en>
        <description_en>Configurations for user.</description_en>
    </group>
    <group>
        <id>scheduling</id>
        <name_en>Configurations for scheduling</name_en>
        <description_en>Configurations for scheduling.</description_en>
    </group>
    <group>
        <id>profiling</id>
        <name_en>Configurations for profiling</name_en>
        <description_en>Configurations for profiling.</description_en>
    </group>
    <group>
        <id>skip</id>
        <name_en>Configurations for skip mode</name_en>
        <description_en>Configurations for skip mode.</description_en>
    </group>
    <group>
        <id>health</id>
        <name_en>Configurations for health check</name_en>
        <description_en>Configurations for health check.</description_en>
    </group>
</configuration>
