Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.0.4-alpha
-
None
-
None
Description
When NMs are decommissioned for non-fault reasons (capacity change etc.), it's desirable to minimize the impact to running applications.
Currently if a NM is decommissioned, all running containers on the NM need to be rescheduled on other NMs. Further more, for finished map tasks, if their map output are not fetched by the reducers of the job, these map tasks will need to be rerun as well.
We propose to introduce a mechanism to optionally gracefully decommission a node manager.
Attachments
Attachments
Issue Links
- depends upon
-
YARN-311 Dynamic node resource configuration: core scheduler changes
-
- Closed
-
- duplicates
-
YARN-671 Add an interface on the RM to move NMs into a maintenance state
-
- Resolved
-
- is blocked by
-
YARN-291 [Umbrella] Dynamic resource configuration
-
- Open
-
-
HADOOP-9160 Adopt Jolokia as the JMX HTTP/JSON bridge.
-
- Open
-
- is related to
-
YARN-671 Add an interface on the RM to move NMs into a maintenance state
-
- Resolved
-
-
YARN-4939 the decommissioning Node should keep alive if NM restart
-
- Resolved
-
-
YARN-1996 Provide alternative policies for UNHEALTHY nodes.
-
- Open
-
- relates to
-
MAPREDUCE-5381 Support graceful decommission of tasktracker
-
- Resolved
-