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

jialei weng updated YARN-4361:
------------------------------
    Description: 
Total resource count mistake:
NodeRemovedSchedulerEvent in ReconnectNodeTransition will reduce the 
newNode.getTotalCapability() in Multi-thread model. Since the RMNode and 
scheduler in different queue. So it cannot guarantee the remove-update-add 
operation in sequence. Sometimes the total resource will reduce the 
newNode.getTotalCapability() when handling NodeRemovedSchedulerEvent.

  was:
Total resource count mistake:
NodeRemovedSchedulerEvent in ReconnectNodeTransition will reduce the 
newNode.getTotalCapability() in Multi-thread model. Since the RMNode and 
scheduler in different queue. So it cannot guarantee the remove-update-add 
operation in sequence. Usually the total resource will reduce the 
newNode.getTotalCapability() when handling NodeRemovedSchedulerEvent.


> Total resource count mistake:NodeRemovedSchedulerEvent in 
> ReconnectNodeTransition will reduce the newNode.getTotalCapability() in 
> Multi-thread model
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4361
>                 URL: https://issues.apache.org/jira/browse/YARN-4361
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.6.2
>            Reporter: jialei weng
>              Labels: patch
>         Attachments: YARN-4361v1.patch
>
>
> Total resource count mistake:
> NodeRemovedSchedulerEvent in ReconnectNodeTransition will reduce the 
> newNode.getTotalCapability() in Multi-thread model. Since the RMNode and 
> scheduler in different queue. So it cannot guarantee the remove-update-add 
> operation in sequence. Sometimes the total resource will reduce the 
> newNode.getTotalCapability() when handling NodeRemovedSchedulerEvent.



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

Reply via email to