hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley" <omal...@apache.org>
Subject Re: [jira] Commented: (HADOOP-4039) Retired jobs are not present in the job list returned to the job-client.
Date Tue, 02 Sep 2008 16:22:06 GMT
> When the number of jobs could get very long, the second option seems better
> - less data from JT to client, accomodates all the above types of listing
> jobs in a single RPC, for e.g., we then won't need a separate
> jobsToComplete. Thoughts?
>

We need to design all of the protocols so that it is easy to page through
them without duplicates. In the task events we did it via:

{code}
TaskCompletionEvent[] getTaskCompletionEvents(JobID jobid, int fromEventId,
       int maxEvents) throws IOException;
{code}

for job status, we need to use time:

{code}
JobStatus[] getJobStatus(long minSubmitDate, int maxJobs) throws
IOException;
{code}

Note that we'd also need to add the submit date to the JobStatus so that you
can page through them with the client. Thoughts?

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message