[YARN-112] Race in localization can cause containers to fail

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.3
• Fix Version/s: 2.1.0-beta
• Component/s: nodemanager
• Hadoop Flags: Reviewed
• Assignee: Omkar Vinit Joshi
• Reporter: Jason Darrell Lowe
• Created: 19/Sep/12 16:11
• Updated: 27/Aug/13 22:15
• Resolved: 09/Apr/13 19:57

Description

On one of our 0.23 clusters, I saw a case of two containers, corresponding to two map tasks of a MR job, that were launched almost simultaneously on the same node. It appears they both tried to localize job.jar and job.xml at the same time. One of the containers failed when it couldn't rename the temporary job.jar directory to its final name because the target directory wasn't empty. Shortly afterwards the second container failed because job.xml could not be found, presumably because the first container removed it when it cleaned up.

Issue Links

• depends upon: HADOOP-9438 LocalFileContext does not throw an exception on mkdir for already existing directory
• is blocked by: YARN-99 Jobs fail during resource localization when private distributed-cache hits unix directory limits
• is blocked by: YARN-467 Jobs fail during resource localization when public distributed-cache hits unix directory limits
• relates to: MAPREDUCE-5138 Fix LocalDistributedCacheManager after YARN-112