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

Junping Du updated YARN-1506:
-----------------------------

    Attachment: YARN-1506-v16.patch

bq. Good point. However, the Node's running status is already checked in 
StateMachine when calling this event hook. The behaviors before sending 
NodeResourceUpdateSchedulerEvent won't change status of RMNode, so we can omit 
the check here?
Sorry. I forget the UNHEALTHY node cases, update it to v16 patch.

> 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
>         Attachments: YARN-1506-v1.patch, YARN-1506-v10.patch, 
> YARN-1506-v11.patch, YARN-1506-v12.patch, YARN-1506-v13.patch, 
> YARN-1506-v14.patch, YARN-1506-v15.patch, YARN-1506-v16.patch, 
> YARN-1506-v2.patch, YARN-1506-v3.patch, YARN-1506-v4.patch, 
> YARN-1506-v5.patch, YARN-1506-v6.patch, YARN-1506-v7.patch, 
> YARN-1506-v8.patch, YARN-1506-v9.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.2#6252)

Reply via email to