hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1963) Support priorities across applications within the same queue
Date Sat, 14 Mar 2015 00:39:38 GMT

    [ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361409#comment-14361409
] 

Vinod Kumar Vavilapalli commented on YARN-1963:
-----------------------------------------------

Assuming integers are supported
 - Do we have a range?  Otherwise, nothing stops users from setting their priority be INTEGER_MAX
and everybody scratching their heads.
 - If we have a range, which side is up? is -20 >20 like unix (isn't intuitive at all to
me) or -20 < 20 (intuitive)?
 - Either ways, it is an implicit decision that needs to be documented and told to users explicitly.
Labels convey that without any of that.
 - What does a negative priority means anything anyways?
 - Admin comes and says "I need a new super-high priority", now your ranges need to be dynamically
size-able.

I don't see a difference between say 10 priorities and 10 labeled priorities, other than that
labels are better in the following
 - They are more *human readable* on the UI and CLIs: "This app has priority 19" doesn't give
much feedback as much as "This app has HIGH priority"
 - Even if we don't want them now, you can let admins create new priorities between two existing
ones, create a new priority lower than the lowest easily etc. With integers, you start with
0-10, then adding one more lower than them all takes them into negative priorities' territory
making it all confusing.
 - Specifying restrictions is very straight forward: for a root.enginnering queue, VERY_HIGH
can be only be used by (u1,u2, g1), HIGH by (u3, u4) and everything else by everyone.

The way I see it, we will provide a predefined set of labeled priorities that should work
for 80% of the clusters, the remaining can define their own set.

> Support priorities across applications within the same queue 
> -------------------------------------------------------------
>
>                 Key: YARN-1963
>                 URL: https://issues.apache.org/jira/browse/YARN-1963
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: api, resourcemanager
>            Reporter: Arun C Murthy
>            Assignee: Sunil G
>         Attachments: 0001-YARN-1963-prototype.patch, YARN Application Priorities Design.pdf,
YARN Application Priorities Design_01.pdf
>
>
> It will be very useful to support priorities among applications within the same queue,
particularly in production scenarios. It allows for finer-grained controls without having
to force admins to create a multitude of queues, plus allows existing applications to continue
using existing queues which are usually part of institutional memory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message