[
https://issues.apache.org/jira/browse/YARN-5787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15611848#comment-15611848
]
Rohith Sharma K S commented on YARN-5787:
-----------------------------------------
Below is the dead lock trace
{noformat}
"AsyncDispatcher event handler":
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.AbstractYarnScheduler.recoverContainersOnNode(AbstractYarnScheduler.java:390)
- waiting to lock <0x000000076f5923c8> (a
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.addNode(FairScheduler.java:917)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:1223)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:1)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM$8.handle(MockRM.java:1100)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM$8.handle(MockRM.java:1)
at
org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:187)
at
org.apache.hadoop.yarn.event.DrainDispatcher$1.run(DrainDispatcher.java:75)
at java.lang.Thread.run(Thread.java:745)
"main":
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x000000076f6d7148> (a
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
at
java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:943)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.nodeUpdate(FairScheduler.java:1044)
- locked <0x000000076f5923c8> (a
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:1238)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:1)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairScheduler.testResourceUpdateDecommissioningNode(TestFairScheduler.java:4741)
{noformat}
> Deadlock cycle in FairScheduler
> --------------------------------
>
> Key: YARN-5787
> URL: https://issues.apache.org/jira/browse/YARN-5787
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
> Reporter: Rohith Sharma K S
>
> While testing YARN-5375 patch, found a dead lock cycle in fairscheduler.
> Basically it was cause by patch. cc:/[~sandflee]
> Even though in reality this scenario does not happen, it would be better to
> handle it from fairscheduler. I am not sure whether it was noticed earlier,
> but just thought it should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
