[
https://issues.apache.org/jira/browse/HADOOP-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreekanth Ramakrishnan updated HADOOP-3930:
-------------------------------------------
Attachment: HADOOP-3930-10.patch
Attaching patch with following changes:
- Made _JobQueueClient_ to default level access instead of public access.
- Renamed methods in _JobSubmissionProtocol_ to
_getQueues()_,_getQueueInfo(queueName)_ and getJobsFromQueue(queueName)_
- Mirrored these methods in _JobClient_.
- Made change in _JobQueueClient_ to use public methods in _JobClient_ to use
these methods for Job Queue querying.
- Added javadoc for all Public classes and public methods introduced by the
patch.
- Removed the map which stored _JobQueueInfo_ in _QueueManager_.
- Changed type of SchedulingInfo in _JobQueueInfo_ to String.
- Constructing _JobQueueInfo_ on fly when requested in _QueueManager_
> 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
> Fix For: 0.19.0
>
> Attachments: 3930-1.patch, HADOOP-3930-10.patch, HADOOP-3930-2.patch,
> HADOOP-3930-3.patch, HADOOP-3930-4.patch, HADOOP-3930-5.patch,
> HADOOP-3930-6.patch, HADOOP-3930-7.patch, HADOOP-3930-8.patch,
> HADOOP-3930-9.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.
