Bulk Operation

YARN-914 RESOURCE_UPDATE event was repeatedly registered in DECOMMISSIONING state

YARN-914 Avoid sending RMNodeResourceupdate event if resource is same

YARN-914 An easy method to exclude a nodemanager from the yarn cluster cleanly

YARN-914 DecommissioningNodesWatcher should get lists of running applications on node from RMNode.

YARN-914 Add option to graceful decommission to not wait for applications

YARN-914 Better utilize gracefully decommissioning node managers

YARN-914 Remove XML excludes file format

YARN-914 Document the current known issue with server-side NM graceful decom

YARN-914 Client-side NM graceful decom is not triggered when jobs finish

YARN-914 Multiple format support (JSON, etc.) for exclude node file in NM graceful decommission with timeout

YARN-914 Clarify DecommissionType.FORCEFUL comment

YARN-914 Server-Side NM Graceful Decommissioning subsequent call behavior

YARN-914 Server-Side NM Graceful Decommissioning with RM HA

YARN-914 Add -client|server argument for graceful decom

YARN-914 Document graceful decommission CLI and usage

YARN-914 RMNodeResourceUpdateEvent update from scheduler can lead to race condition

YARN-914 Automatic and Asynchronous Decommissioning Nodes Status Tracking

YARN-914 UI changes for decommissioning node

YARN-914 New parameter or CLI for decommissioning node gracefully in RMAdmin CLI

YARN-914 Notify AM with containers (on decommissioning node) could be preempted after timeout.

YARN-914 Resource update during NM graceful decommission

YARN-914 RMNode State Transition Update with DECOMMISSIONING state

YARN-914 RM to inform AMs when a container completed due to NM going offline -planned or unplanned