[ 
https://issues.apache.org/jira/browse/YARN-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647507#comment-14647507
 ] 

Rohith Sharma K S commented on YARN-3250:
-----------------------------------------

bq. I think one problem is that if there's ever a value set in state-store, RM 
cannot pick up the value using the config any more
I see, I agree. configuration files would become stale after one 
restart/switch. How about having command that read yarn-site.xml specific 
configurations very likely similar to {{./yarn rmadmin refreshAdminAcls}}.This 
read *yarn.admin.acl* from yarn-site.xml configuration when refreshAdminAcls 
invoked. Similar line, setting cluster-max-application-priorty would be 
{{./yarn rmadmin refreshClusterMaxPriority}} or {{./yarn rmadmin 
refreshClusterPriority}}. Thoughts?

bq. How about yarn application <ApplicationId> -setPriority <priority> ?
Make sense.

> Support admin/user cli interface in for Application Priority
> ------------------------------------------------------------
>
>                 Key: YARN-3250
>                 URL: https://issues.apache.org/jira/browse/YARN-3250
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Sunil G
>            Assignee: Rohith Sharma K S
>
> Current Application Priority Manager supports only configuration via file. 
> To support runtime configurations for admin cli and REST, a common management 
> interface has to be added which can be shared with NodeLabelsManager. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to