[
https://issues.apache.org/jira/browse/HADOOP-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644229#action_12644229
]
Hemanth Yamijala commented on HADOOP-4471:
------------------------------------------
Had an offline discussion with Sameer, Owen and Vivek, and we concluded that
for the time being we *should* sort the jobs in the running queue. We recognize
this could cause a priority inversion problem. However, not sorting seemed
extremely counter-intuitive to what the user would expect. There is also no way
in which the user can workaround the problem of bumping the priority of his
jobs and getting them to run, short of killing other jobs ahead in the queue.
Given these points, we think it will be a good idea to:
- sort the jobs in the running queue as part of this jira.
- solve the problem of priority inversion in a separate jira that can be looked
at a little later.
> 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: Sreekanth Ramakrishnan
> Priority: Blocker
> Fix For: 0.19.1
>
> 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.
