[ https://issues.apache.org/jira/browse/YARN-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856757#comment-13856757 ]
Bikas Saha commented on YARN-1506: ---------------------------------- Per operation vs configuration makes sense. I would just like to avoid this reconfiguration from spreading to parts of the code where it does not need to. > Replace set resource change on RMNode/SchedulerNode directly with event > notification. > ------------------------------------------------------------------------------------- > > Key: YARN-1506 > URL: https://issues.apache.org/jira/browse/YARN-1506 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager, scheduler > Reporter: Junping Du > Assignee: Junping Du > Priority: Blocker > > According to Vinod's comments on YARN-312 > (https://issues.apache.org/jira/browse/YARN-312?focusedCommentId=13846087&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13846087), > we should replace RMNode.setResourceOption() with some resource change event. -- This message was sent by Atlassian JIRA (v6.1.5#6160)