[MAPREDUCE-4139] Potential ResourceManager deadlock when SchedulerEventDispatcher is stopped

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.3
• Fix Version/s: 0.23.3, 2.0.2-alpha
• Component/s: mrv2
• Target Version/s: 0.23.3
• Assignee: Jason Darrell Lowe
• Reporter: Jason Darrell Lowe
• Created: 11/Apr/12 21:30
• Updated: 11/Oct/12 17:48
• Resolved: 17/Apr/12 22:41

Description

When the main thread calls ResourceManager$SchedulerEventDispatcher.stop() it grabs a lock on the object, kicks the event processor thread, and then waits for the thread to exit. However the interrupted event processor thread can end up trying to call the synchronized getConfig() method which results in deadlock.

Issue Links

• is part of: MAPREDUCE-3942 Randomize master key generation for ApplicationTokenSecretManager and roll it every so often