[ 
https://issues.apache.org/jira/browse/YARN-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohith Sharma K S updated YARN-3250:
------------------------------------
    Attachment: 0002-YARN-3250.patch

Thanks [~sunilg] for the review.. Updating the patch with review comments fix.

The {{refreshClusterMaxPriority}} admin command updates the cluster max 
priority variable in Abstractyarnscheduler. The updated max priority is affects 
only for the applications which are submitted after refreshing. For the 
existing submitted applications, old cluster max priority has taken 
considerations. And in the web UI also, application priority display more than 
cluster max priority when the refreshing max priority by shrinking it. This 
behavior should be documented such that decreasing max cluster priority value 
affects only for applications submitted later. The running applications 
continues to be running without any affect of refreshClusterMaxPriority.


> Support admin 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
>         Attachments: 0001-YARN-3250-V1.patch, 0002-YARN-3250.patch
>
>
> 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