[
https://issues.apache.org/jira/browse/MAPREDUCE-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166649#comment-13166649
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-3519:
----------------------------------------------------
Configuration seems to have a host of other synchronization problems, we are
either lucky to not hit them or plain ignorant.
Looked at the latest patch. This is fine especially in the light of [Ravi's
comment|https://issues.apache.org/jira/browse/MAPREDUCE-3519?focusedCommentId=13166065&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13166065]
above.
+1.
> Deadlock in LocalDirsHandlerService and ShuffleHandler
> ------------------------------------------------------
>
> Key: MAPREDUCE-3519
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3519
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2, nodemanager
> Affects Versions: 0.23.1, 0.24.0
> Reporter: Ravi Gummadi
> Assignee: Ravi Gummadi
> Priority: Blocker
> Fix For: 0.23.1
>
> Attachments: 3519.patch, 3519.v1.patch, deadlock.txt
>
>
> MAPREDUCE-3121 cloned Configuration object in LocalDirsHandlerService.init()
> to avoid others to access that configuration object. But since it is used in
> local FileSystem object creation in LocalDirAllocator.AllocatorPerContext and
> the same FileSystem object is used in
> ShuffleHandler.Shuffle.localDirAllocator, this is causing a deadlock when
> accessing this configuration object from LocalDirsHandlerService and
> ShuffleHandler along with AllocatorPerContext object.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
