[
https://issues.apache.org/jira/browse/MAPREDUCE-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Gummadi updated MAPREDUCE-3519:
------------------------------------
Description: 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. (was: MAPREDUCE-3121
cloned Configuration object in LocalDirsHandlerService.init() to avoid others
to access that configuration object. But since it is set in the base class of
LocalDirsHandlerService using super.init(conf), it is reflected and is
accessible to some other services. This is causing a deadlock when accessing
this configuration object from LocalDirsHandlerService and ShuffleHandler along
with AllocatorPerContext object.)
> 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
> Fix For: 0.23.1
>
> Attachments: 3519.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
