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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2008/09/02 11:34: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=12627616#action_12627616 ]
Vinod Kumar Vavilapalli commented on HADOOP-4039:
-------------------------------------------------
This list might get long depending upon how long job-status information is persisted in DFS, which is given by the value of mapred.job.tracker.persist.jobstatus.hours specified in hours. So, in similar lines, we can have a "-n NoOfHours" option to -list option, defaulting it to 24 hours.
> 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.