[
https://issues.apache.org/jira/browse/HADOOP-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625294#action_12625294
]
Hemanth Yamijala commented on HADOOP-3930:
------------------------------------------
A couple of points if we are moving towards Owen's proposal:
- In Sreekanth's comment above, he's mentioned that the attached patch adds one
column for each entry in the Map returned by {{get...SchedulingInfo()}} APIs.
The other option, of course, is to display all scheduling info in a single
column.
-- The advantage of the multi-column approach is purely usability and
aesthetics (schedulers which have per queue scheduling info will show only a
name, and the scheduling info as a string, which will look quite odd). Also, it
will allow changes to the UI easier, IMHO.
-- The advantage of the single column approach is simplicity for the current
implementation.
- I personally prefer multi-column, but willing to go with consensus.
- If we go with the multi-column approach though, building scheduling
information out of a {{toString}} API becomes harder.
- If we do go with Owen's approach, I think we might also need:
{code}
class TaskScheduler {
Object getSchedulerInfo(String queueName);
}
{code}
to handle cases where the scheduler has a per queue specific info.
Please try to vote on your preferred UI approach, if any, so we can move this
forward.
> 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
> Affects Versions: 0.17.2
> Reporter: Matei Zaharia
> Assignee: Sreekanth Ramakrishnan
> Priority: Minor
> Attachments: 3930-1.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.
