You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2008/08/31 18:47:44 UTC
[jira] Commented: (HADOOP-4039) Retired jobs are not present in the
job list returned to the job-client.
[ https://issues.apache.org/jira/browse/HADOOP-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627318#action_12627318 ]
Owen O'Malley commented on HADOOP-4039:
---------------------------------------
In the future this list will get very long. It probably makes sense to add a parameter that specifies the earliest date of jobs they are interested in seeing and defaulting it to 1 day ago.
> Retired jobs are not present in the job list returned to the job-client.
> ------------------------------------------------------------------------
>
> Key: HADOOP-4039
> URL: https://issues.apache.org/jira/browse/HADOOP-4039
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
>
> After {{mapred.jobtracker.retirejob.interval}} elapses, completed jobs are no longer maintained by the JT, but instead when job-client ask for job status, counters or task completion events, the relevant information is picked up from completed job store. But a retired job is not listed in the output of "{{hadoop job -list all}}", without which other information from completed job store isn't quite useful unless a job-id is known from elsewhere.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.