hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1963) Support priorities across applications within the same queue
Date Fri, 10 Apr 2015 14:09:15 GMT

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

Jason Lowe commented on YARN-1963:
----------------------------------

Part of the concern with the above proposal is that we're mapping labels to numbers, and that
range is packed tight.  If someone needs a priority like MEDIUM_HIGH then we have to dynamically
remap the label to number mapping _and_ update all existing priorities for applications (since
we mapped them to numbers for performance in the scheduling algorithms).

For me it comes back to my previous comment: priorities are meaningless unless compared to
other priorities.  It's easy to reason about numerical comparisons, many other systems already
do this, and IMHO we can keep things simple initially.  If we need to add label aliases we
can always extend the API to do this later.

If everyone else feels like we _have_ to have labels out of the gate then I won't block it,
but I'd like to see the basic functionality working before we complicate it.

> 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