[
https://issues.apache.org/jira/browse/YARN-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912521#comment-16912521
]
Eric Payne commented on YARN-9760:
----------------------------------
[~jhung], thanks for raising this interesting feature request.
In order to avoid making the RM even more complex than it already is, I am a
little concerned about adding more features to YARN that could possibly be done
different ways. For example, creating separate subqueues for different
priorities and using the queue priority feature. Or, writing a custom script on
the client side that that does this analysis at submission time.
I just want to avoid further complicating YARN if we don't have to. Thoughts?
> Support configuring application priorities on a workflow level
> --------------------------------------------------------------
>
> Key: YARN-9760
> URL: https://issues.apache.org/jira/browse/YARN-9760
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Jonathan Hung
> Assignee: Varun Saxena
> Priority: Major
> Labels: release-blocker
>
> Currently priorities are submitted on an application level, but for end users
> it's common to submit workloads to YARN at a workflow level. This jira
> proposes a feature to store workflow id + priority mappings on RM (similar to
> queue mappings). If app is submitted with a certain workflow id (as set in
> application submission context) RM will override this app's priority with the
> one defined in the mapping.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
