[ https://issues.apache.org/jira/browse/YARN-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863865#comment-13863865 ]
Junping Du commented on YARN-1506: ---------------------------------- bq. I thought this way before as following common practice. However, given we agreed that some information (OvercommitTimeout) is unnecessary to go to RMNode and cached there. I think it could be better to send separated events to RMNode and Scheduler by AdminService. Thoughts? Just think it again, another simpler way may be we just sent event with OvercommitTimeout to RMNode but not cached there and send scheduler event in RMNode transition. Will update patch soon. > 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 > Attachments: YARN-1506-v1.patch, YARN-1506-v2.patch, > YARN-1506-v3.patch, YARN-1506-v4.patch > > > 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)