[
https://issues.apache.org/jira/browse/YARN-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944890#comment-16944890
]
Jonathan Hung commented on YARN-9760:
-------------------------------------
[~varun_saxena], thanks for the 03 patch. I was able to get the TestMRJobs test
case to succeed by taking out the lines you added in the setup function:
{noformat}
conf.set(YarnConfiguration.SCHEDULER_CONFIGURATION_STORE_CLASS,
YarnConfiguration.MEMORY_CONFIGURATION_STORE); {noformat}
and taking out the hadoop-mapreduce-client-jobclient capacity-scheduler.xml
file. Seems like this might be a bug with the mutable cs configuration
provider (but unrelated to this patch).
Could you attach a patch with these two changes? Thanks!
> 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
> Attachments: YARN-9760.01.patch, YARN-9760.02.patch,
> YARN-9760.03.patch
>
>
> 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.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
