Details
-
Bug
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
If a container is killed while localizing then it releases all of its resources. If the resource count goes to zero and it is in the DOWNLOADING state then the resource bookkeeping is removed in the resource tracker. Shortly afterwards the localizer could heartbeat in and report the successful localization of the resource that was just removed. When the LocalResourcesTrackerImpl receives the LOCALIZED event but does not find the corresponding LocalResource for the event then it simply logs a "localized without a location" warning. At that point I think the localized resource has been leaked on the disk since the NM has removed bookkeeping for the resource without removing it on disk.