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

Jian He commented on YARN-3887:
-------------------------------

thanks Sunil, for below, I think we can add a appPriorityUpdated method in 
OrderingPolicy and follow the implementation of demandUpdated method. Doing 
that, the synchronization of queue may not be needed.
{code}
    synchronized (queue) {
      queue.getOrderingPolicy().removeSchedulableEntity(
          application.getCurrentAppAttempt());

      // Update new priority in SchedulerApplication
      application.setPriority(appPriority);

      queue.getOrderingPolicy().addSchedulableEntity(
          application.getCurrentAppAttempt());
    }{code}

> Support for changing Application priority during runtime
> --------------------------------------------------------
>
>                 Key: YARN-3887
>                 URL: https://issues.apache.org/jira/browse/YARN-3887
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler, resourcemanager
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: 0001-YARN-3887.patch, 0002-YARN-3887.patch, 
> 0003-YARN-3887.patch, 0004-YARN-3887.patch, 0005-YARN-3887.patch
>
>
> After YARN-2003, adding support to change priority of an application after 
> submission. This ticket will handle the server side implementation for same.
> A new RMAppEvent will be created to handle this, and will be common for all 
> schedulers.



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

Reply via email to