[
https://issues.apache.org/jira/browse/YARN-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13969919#comment-13969919
]
Vinod Kumar Vavilapalli edited comment on YARN-1929 at 4/15/14 7:07 PM:
------------------------------------------------------------------------
Started looking at it. One question: This only happens when somebody explicitly
tries to stop the RM overall, right? Trying to understanding if this can happen
during any fail-over or only during shutdown + concurrent fail-over.
was (Author: vinodkv):
Started looked at it. One question: This only happens when somebody explicitly
tries to stop the RM overall, right? Trying to understanding if this can happen
during any fail-over or only during shutdown + concurrent fail-over.
> DeadLock in RM when automatic failover is enabled.
> --------------------------------------------------
>
> Key: YARN-1929
> URL: https://issues.apache.org/jira/browse/YARN-1929
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Environment: Yarn HA cluster
> Reporter: Rohith
> Assignee: Karthik Kambatla
> Priority: Blocker
> Attachments: yarn-1929-1.patch, yarn-1929-2.patch
>
>
> Dead lock detected in RM when automatic failover is enabled.
> {noformat}
> Found one Java-level deadlock:
> =============================
> "Thread-2":
> waiting to lock monitor 0x00007fb514303cf0 (object 0x00000000ef153fd0, a
> org.apache.hadoop.ha.ActiveStandbyElector),
> which is held by "main-EventThread"
> "main-EventThread":
> waiting to lock monitor 0x00007fb514750a48 (object 0x00000000ef154020, a
> org.apache.hadoop.yarn.server.resourcemanager.EmbeddedElectorService),
> which is held by "Thread-2"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
