[YARN-72] NM should handle cleaning up containers when it shuts down

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.3-alpha, 0.23.6
• Component/s: nodemanager
• Assignee: Sandy Ryza
• Reporter: Hitesh Shah
• Created: 22/Feb/12 02:10
• Updated: 04/Aug/14 22:22
• Resolved: 03/Dec/12 12:14

Description

Ideally, the NM should wait for a limited amount of time when it gets a shutdown signal for existing containers to complete and kill the containers ( if we pick an aggressive approach ) after this time interval.

For NMs which come up after an unclean shutdown, the NM should look through its directories for existing container.pids and try and kill an existing containers matching the pids found.

Issue Links

• blocks: YARN-71 Ensure/confirm that the NodeManager cleans up local-dirs on restart
• depends upon: YARN-170 NodeManager stop() gets called twice on shutdown
• duplicates: YARN-74 nodemanager should cleanup running containers when shutdown
• relates to: YARN-73 nodemanager should cleanup running containers when it starts
• relates to: YARN-495 Change NM behavior of reboot to resync