Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <2008172542.1234339380280.JavaMail.jira@brutus>
Date: Wed, 11 Feb 2009 00:03:00 -0800 (PST)
From: "Yiping Han (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5187) Provide an option to turn off
 priorities in jobs
In-Reply-To: <1765950051.1233919679686.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-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672542#action_12672542 ] 

Yiping Han commented on HADOOP-5187:
------------------------------------

Regarding distribution of excess capacity. Should we have a priority mode between queues. Say, queues are given priorities, so when there are excess capacity, they are given to the queues with highest priority first.

I agree with Vinod, this should be made pluggable.

> Provide an option to turn off priorities in jobs
> ------------------------------------------------
>
>                 Key: HADOOP-5187
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5187
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: contrib/fair-share
>            Reporter: Hemanth Yamijala
>            Priority: Minor
>
> The fairshare scheduler can define pools mapping to queues (as defined in the capacity scheduler - HADOOP-3445). When used in this manner, one can imagine queues set up to be used by users who come from disparate teams or organizations (say a default queue). For such a queue, it makes sense to ignore job priorities and consider the queue as strict FIFO, as it is difficult to compare priorities of jobs from different users. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.