[YARN-4331] Restarting NodeManager leaves orphaned containers

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Not A Problem
• Affects Version/s: 2.7.1
• Component/s: nodemanager, yarn
• Assignee: Unassigned
• Reporter: Joseph Francis
• Created: 04/Nov/15 18:48
• Updated: 09/Nov/15 14:02
• Resolved: 09/Nov/15 14:01

Description

We are seeing a lot of orphaned containers running in our production clusters.
I tried to simulate this locally on my machine and can replicate the issue by killing nodemanager.
I'm running Yarn 2.7.1 with RM state stored in zookeeper and deploying samza jobs.
Steps:

1. Deploy a job
2. Issue a kill -9 signal to nodemanager
3. We should see the AM and its container running without nodemanager
4. AM should die but the container still keeps running
5. Restarting nodemanager brings up new AM and container but leaves the orphaned container running in the background

This is effectively causing double processing of data.