Sunil G commented on YARN-4413:

Hi [~templedf]
Thank you for the updated patch.

I have some doubts on the updated patch. I am not very sure about the move from 
DECOMMISSIONED to SHUTDOWN on RECOMMISSION event. Event doesnt sounds so clean 
or correct. Why could we not send SHUTDOWN event itself. I see no harm in doing 
Because after refresh, a node is found to be in valid state as per config but 
DECOMMISSIONED by RM. So such nodes can be moved via SHUTDOWN event. Please 
correct me if I am missing something here.

> Nodes in the includes list should not be listed as decommissioned in the UI
> ---------------------------------------------------------------------------
>                 Key: YARN-4413
>                 URL: https://issues.apache.org/jira/browse/YARN-4413
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.7.1
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
>         Attachments: YARN-4413.001.patch
> If I decommission a node and then move it from the excludes list back to the 
> includes list, but I don't restart the node, the node will still be listed by 
> the web UI as decomissioned until either the NM or RM is restarted.  Ideally, 
> removing the node from the excludes list and putting it back into the 
> includes list should cause the node to be reported as shutdown instead.
> CC [~kshukla]

This message was sent by Atlassian JIRA

Reply via email to