[
https://issues.apache.org/jira/browse/MAPREDUCE-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated MAPREDUCE-1098:
-------------------------------------
Attachment: MAPREDUCE-1098.patch
bq. Oh, sure. I think making the reference count atomic is reasonable.
Owen pointed out today that we don't need to synchronize on CacheStatus to
incremement/decrement/check the CacheStatus.refcount since we are synchronized
on the global TrackerDistributedCacheManager.cachedArchives lock anyway... we
should fix localizeCache to never use CacheStatus.refcount.
> Incorrect synchronization in DistributedCache causes TaskTrackers to freeze
> up during localization of Cache for tasks.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1098
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1098
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Reporter: Sreekanth Ramakrishnan
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1098.patch, MAPREDUCE-1098.patch,
> patch-1098-0.20.txt, patch-1098-1.txt, patch-1098-2.txt,
> patch-1098-ydist.txt, patch-1098.txt
>
>
> Currently {{org.apache.hadoop.filecache.DistributedCache.getLocalCache(URI,
> Configuration, Path, FileStatus, boolean, long, Path, boolean)}} allows only
> one {{TaskRunner}} thread in TT to localize {{DistributedCache}} across jobs.
> Current way of synchronization is across baseDir this has to be changed to
> lock on the same baseDir.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
