[
https://issues.apache.org/jira/browse/MAPREDUCE-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886618#action_12886618
]
Amareshwari Sriramadasu commented on MAPREDUCE-1920:
----------------------------------------------------
bq. According to a comment in JobTracker#retireJob()
mapreduce.jobtracker.retirejobs is "primarily for testing" (I assume because if
you set it to true on a real installation the JT eventually runs out of
memory?).
Yes. The configuration is only for testing. If mapreduce.jobtracker.retirejobs
is set to false, the jobs will never be retired.
Currently, JobTracker maintains a retired job cache which holds JobStatus of
the retired jobs, but it does not hold counters. If we enable completed job
store by default, the data(JobStatus) will be duplicated. I think we should
leave the default configuration as is and let users enable completed job store
if they are interested in counters. Also, we should mark MAPREDUCE-870 an
incompatible change and update the release note.
Thoughts?
> Job.getCounters() returns null when using a cluster
> ---------------------------------------------------
>
> Key: MAPREDUCE-1920
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1920
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.21.0
> Reporter: Aaron Kimball
> Assignee: Tom White
> Priority: Critical
> Attachments: MAPREDUCE-1920.patch
>
>
> Calling Job.getCounters() after the job has completed (successfully) returns
> null.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
