[
https://issues.apache.org/jira/browse/YARN-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929810#comment-16929810
]
Varun Saxena commented on YARN-9760:
------------------------------------
Sorry, I missed the comments here. [~eepayne], as Jonathan explained we wanted
cluster admins to control the priority, hence the feature.
[~jhung], we can use YARN tags to get workflow information as we do in timeline
service. By leveraging queue mapping interface, I guess you mean the
PlacementRule interface. That though is meant primarily for queue placement,
the way it is defined right now. We can potentially have a new interface, once
we have more other use cases for setting priority i.e. based on something other
than workflows?
> 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
