[YARN-3212] RMNode State Transition Update with DECOMMISSIONING state

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: graceful, resourcemanager
• Target Version/s: 2.8.0
• Hadoop Flags: Reviewed
• Assignee: Junping Du
• Reporter: Junping Du
• Created: 18/Feb/15 17:48
• Updated: 25/Oct/19 20:27
• Resolved: 18/Sep/15 17:08

Description

As proposed in YARN-914, a new state of “DECOMMISSIONING” will be added and can transition from “running” state triggered by a new event - “decommissioning”.
This new state can be transit to state of “decommissioned” when Resource_Update if no running apps on this NM or NM reconnect after restart. Or it received DECOMMISSIONED event (after timeout from CLI).
In addition, it can back to “running” if user decides to cancel previous decommission by calling recommission on the same node. The reaction to other events is similar to RUNNING state.

Issue Links

• blocks: YARN-3223 Resource update during NM graceful decommission
• depends upon: YARN-3225 New parameter or CLI for decommissioning node gracefully in RMAdmin CLI
• depends upon: YARN-3445 Cache runningApps in RMNode for getting running apps on given NodeId
• is depended upon by: YARN-3224 Notify AM with containers (on decommissioning node) could be preempted after timeout.
• is duplicated by: YARN-670 Add an Exception to indicate 'Maintenance' for NMs and add this to the JavaDoc for appropriate protocols