hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4039) Retired jobs are not present in the job list returned to the job-client.
Date Fri, 05 Sep 2008 05:33:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628553#action_12628553

Owen O'Malley commented on HADOOP-4039:

Passing Filters across RPC is a bad plan. I'd suggest something like:


JobStatus[] getJobStatus(long minSubmitDate, int maxJobs, JobState filter) throws IOException;

and handle the filter = null as no filter. That would let you page through the results *and*
do the server side filtering. You may also want to add a filter for the user, since that will
be another common operation.

> 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.

View raw message