[YARN-6641] Non-public resource localization on a bad disk causes subsequent containers failure

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.0
• Fix Version/s: 2.9.0, 3.0.0-alpha4, 2.8.2
• Hadoop Flags: Reviewed
• Assignee: Kuhu Shukla
• Reporter: Kuhu Shukla
• Created: 24/May/17 19:43
• Updated: 24/Apr/18 20:51
• Resolved: 26/May/17 14:47

Description

YARN-3591 added the checkLocalResource method to isResourcePresent() call to allow checking an already localized resource against the list of good/full directories.

Since LocalResourcesTrackerImpl instantiations for app level resources and private resources do not use the new constructor, such resources that are on bad disk will never be checked against good dirs.