[
https://issues.apache.org/jira/browse/YARN-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864806#comment-13864806
]
Jian He commented on YARN-1506:
-------------------------------
bq. REBOOT -> RUNNING for a rebooted node come back as running for accepting
RECONNECTED/CLEAN_CONTAINER/AP
not sure about this. A restart node seems only trigger the RECONNECT event on
register and RMNode stays on RUNNING when receiving this event.
bq. DECOMMISSIONED -> RUNNING for a decommissioned node be recommissoned again
simply because we are not supporting recommission ?
bq. LOST -> NEW/UNHELATHY/DECOMMISSONED for a expired node heartbeat again
from the code, I can see the node is actually gone from RM's point of view once
the node expires
bq. UNHEALTHY -> RUNNING for a unhealthy node report to be healthy again
this is handled
> 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, YARN-1506-v5.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)
