hadoop2.2.0 mapred-site.xml

<property>
<name>mapreduce.jobtracker.jobhistory.location</name>
<value></value>
<description> 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.
</description>
</property>

<property>
<name>mapreduce.jobtracker.jobhistory.task.numberprogresssplits</name>
<value>12</value>
<description> Every task attempt progresses from 0.0 to 1.0 [unless
it fails or is killed].  We record, for each task attempt, certain
statistics over each twelfth of the progress range.  You can change
the number of intervals we divide the entire range of progress into
by setting this property.  Higher values give more precision to the
recorded data, but costs more memory in the job tracker at runtime.
Each increment in this attribute costs 16 bytes per running task.
</description>
</property>

<property>
<name>mapreduce.job.userhistorylocation</name>
<value></value>
<description> 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".
</description>
</property>

<property>
<name>mapreduce.jobtracker.jobhistory.completed.location</name>
<value></value>
<description> The completed job history files are stored at this single well
known location. If nothing is specified, the files are stored at
${mapreduce.jobtracker.jobhistory.location}/done.
</description>
</property>

<property>
<name>mapreduce.job.committer.setup.cleanup.needed</name>
<value>true</value>
<description> true, if job needs job-setup and job-cleanup.
false, otherwise
</description>
</property>