Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <357388675.1226594564696.JavaMail.jira@brutus>
Date: Thu, 13 Nov 2008 08:42:44 -0800 (PST)
From: "Hudson (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-4471) Capacity Scheduler should maintain
 the right ordering of jobs in its running queue
In-Reply-To: <1920306785.1224578744405.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647327#action_12647327 ] 

Hudson commented on HADOOP-4471:
--------------------------------

Integrated in Hadoop-trunk #660 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/660/])
    . Sort running jobs by priority in the capacity scheduler. Contributed by Amar Kamat.


> 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.