[
https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149696#comment-14149696
]
Sunil G commented on YARN-1963:
-------------------------------
Thank you [~maysamyabandeh] for providing us the use cases.
1.
bq.use case seems to be mentioned in Item 3 of Section 1.5.3
Yes. By changing priority of an application at runtime, will help to over come
the scenario mentioned by you. I will in-cooperate the same by providing more
scenarios and impacts about it.
2.
bq.priority can also be incorporated to the fair share calculation
Application Priority will be supported by both schedulers. And there are sub
jiras opened for same, however we can re allign the same w.r.t the same base
design, and I will include changes from Fair also. As of now priority labels
and internal implementation will be common, however separate ACL/per queue
priority-label configurations will be required per scheduler level. In future,
when both scheduler shares same config and common code, this can be pulled out
as common code. For now, configurations and its specific implementation can be
done separate for both schedulers. Sub jiras will be split ted accordingly
> 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
>
>
> 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)
