[
https://issues.apache.org/jira/browse/HADOOP-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655119#action_12655119
]
Vinod K V commented on HADOOP-4471:
-----------------------------------
Forrest documentation (0.19) for capacity scheduler still maintains that "once
a job is running, it will not be preempted for a higher priority job". Need to
fix this.
> Capacity Scheduler should maintain the right ordering of jobs in its running
> queue
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-4471
> URL: https://issues.apache.org/jira/browse/HADOOP-4471
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Affects Versions: 0.19.0
> Reporter: Vivek Ratan
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: HADOOP-4471-v1.patch
>
>
> Currently, the Capacity Scheduler maintains a simple linked list of jobs
> which are running. This implies that running jobs are sorted by when they
> started running (i.e., when they were added to the queue). The Scheduler
> should maintain the same ordering among running jobs that it does for waiting
> jobs. Jobs should be sorted by priority (if the queue supports priorities)
> and by their submit time.
> This sorting would be more fair in deciding which running jobs get access to
> a free TT. It also does not penalize jobs that have a longer setup task,
> which affects when they enter the run queue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
