[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327196#comment-14327196
]
Devaraj K commented on YARN-1963:
---------------------------------
I would also agree for numbers rather than labels for not to make it more complex. If we are
moving with numbers, I think we can just use the existing priority API from ApplicationSubmissionContext.setPriority(Priority
priority) and not required any new API's to expose to clients.
We may need to think for M/R Job priory case, M/R Job supports enums for priority (i.e. VERY_HIGH,
HIGH, NORMAL, LOW, VERY_LOW) and we need to have some mechanism to map these enums to priority
numbers.
> 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: 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)
|