[
https://issues.apache.org/jira/browse/MAPREDUCE-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885843#action_12885843
]
Aaron Kimball commented on MAPREDUCE-1920:
------------------------------------------
I agree that this shouldn't break :) And yet, I configured MapReduce as a
straight-up pseudo-distributed instance. I didn't set anything other than
mapred.job.tracker and fs.default.name in the conf files.
My application calls job.getCounters() immediately upon return from
job.waitForCompletion(). It may be possible that jobs are retiring
instantaneously / "very quickly" in a manner that is racing with my
application? Is there a guaranteed window of time for which a job won't be
retired?
I feel like there should be a guaranteed minimum; maybe this is in time, maybe
as long as the original reference to a Job object on the client is live?
(Easier said than done in the latter case -- maybe the Job could be configured
in such a way as to reserve the right to retrieve its Counters or other
post-execution data at least once after waitForCompletion() returns?)
> 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
> Priority: Critical
>
> 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.
