Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.5.0
-
None
-
None
-
Reviewed
Description
Occasionally the MapReduce AM can "get stuck" trying to shut down. MAPREDUCE-6049 and MAPREDUCE-5888 were specific instances that have been fixed, but this can also occur with uber jobs if the task code inadvertently leaves non-daemon threads lingering.
We should explicitly shutdown the JVM after the MapReduce AM has unregistered and all services have been stopped.