hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3930) Decide how to integrate scheduler info into CLI and job tracker web page
Date Tue, 16 Sep 2008 15:30:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631433#action_12631433
] 

Hemanth Yamijala commented on HADOOP-3930:
------------------------------------------

bq. Left jobsToComplete as is.
I was thinking of something like:
{code}
private JobStatus[] getJobStatus(Collection<JobInProgress> jips, boolean onlyRunning)
{
  // ..
  if (onlyRunning) {
    // consider only jobs which are running or prep.
  }
}
{code}

Would that work ?

Regarding tests, taking cue from APIs like {{getAllJobs}}, I think it is OK to provide wrapper
APIs around the queue info related methods. These could be package private and the test case
can directly access these. So, something like:
{code}
JobQueueInfo[] getJobQueueInfos() { return jobSubmitClient.getJobQueueInfos(); }
private void displayQueueList() {
  JobQueueInfo[] queues = getJobQueueInfos();
  //
}
{code}

Agree with rest of your explanations.

> Decide how to integrate scheduler info into CLI and job tracker web page
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-3930
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3930
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>    Affects Versions: 0.19.0
>            Reporter: Matei Zaharia
>            Assignee: Sreekanth Ramakrishnan
>         Attachments: 3930-1.patch, HADOOP-3930-2.patch, HADOOP-3930-3.patch, HADOOP-3930-4.patch,
HADOOP-3930-5.patch, mockup.JPG
>
>
> We need a way for job schedulers such as HADOOP-3445 and HADOOP-3476 to provide info
to display on the JobTracker web interface and in the CLI. The main things needed seem to
be:
> * A way for schedulers to provide info to show in a column on the web UI and in the CLI
- something as simple as a single string, or a map<string, int> for multiple parameters.
> * Some sorting order for jobs - maybe a method to sort a list of jobs.
> Let's figure out what the best way to do this is and implement it in the existing schedulers.
> My first-order proposal at an API: Augment the TaskScheduler with
> * public Map<String, String> getSchedulingInfo(JobInProgress job) -- returns key-value
pairs which are displayed in columns on the web UI or the CLI for the list of jobs.
> * public Map<String, String> getSchedulingInfo(String queue) -- returns key-value
pairs which are displayed in columns on the web UI or the CLI for the list of queues.
> * public Collection<JobInProgress> getJobs(String queueName) -- returns the list
of jobs in a given queue, sorted by a scheduler-specific order (the order it wants to run
them in / schedule the next task in / etc).
> * public List<String> getQueues();

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message