[
https://issues.apache.org/jira/browse/YARN-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913621#comment-16913621
]
Jonathan Hung commented on YARN-9760:
-------------------------------------
Hi [~eepayne], thanks for the comments. I understand the concern. The reason we
implemented it this way was b/c we wanted queue admins to be able to set
workflow priorities themselves (i.e. leveraging YARN queue ACLs) which would be
difficult to do client-side.
IMO there's not too much complexity for this feature on the RM side. But to
minimize overall complexity, perhaps we can do this in a way that doesn't make
protocol changes, and on the RM side we can leverage the queue mapping
interface. Would this address your concerns? [~varun_saxena] how does this
sound?
> 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
