|
This issue incorporates:
|
|
HADOOP-4035
Modify the capacity scheduler (HADOOP-3445) to schedule tasks based on memory requirements and task trackers free memory
|
|
|
|
 |
|
MAPREDUCE-534 Provide accounting functionality for Hadoop resource manager
|
|
|
|
|
|
HADOOP-3698
Implement access control for submitting jobs to queues in the JobTracker
|
|
|
|
|
|
HADOOP-3699
Create a UI for viewing configured queues and related information
|
|
|
|
|
|
HADOOP-3245
Provide ability to persist running jobs (extend HADOOP-1876)
|
|
|
|
|
|
HADOOP-3479
Implement configuration items useful for Hadoop resource manager (v1)
|
|
|
|
|
|
HADOOP-3445
Implementing core scheduler functionality in Resource Manager (V1) for Hadoop
|
|
|
|
|
|
HADOOP-3930
Decide how to integrate scheduler info into CLI and job tracker web page
|
|
|
|
|
|
HADOOP-3759
Provide ability to run memory intensive jobs without affecting other running tasks on the nodes
|
|
|
|
|
HADOOP-3581
Prevent memory intensive user tasks from taking down nodes
|
|
|
|
New Feature
It is proposed that today's JT be extended to support queues of jobs (actually, JobInProgress objects). The JobQueueManager handles these queues, which are persisted to disk. Users can interact with the queues, which are configured appropriately.
The JT today handles at least three separate functionalities: scheduling, monitoring, and Web serving. It is likely that in the future, these three are separated out, at least in terms of components/modules/classes within JT, if not outside it.