[
https://issues.apache.org/jira/browse/YARN-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984699#comment-13984699
]
Vinod Kumar Vavilapalli commented on YARN-1929:
-----------------------------------------------
Seems 'fine' to me. It is one of those
fine-for-now-but-not-sure-if-anything-else-is-broken.
OTOH, we aren't getting rid of the remaining locking in CompositeService.
Something that we should fix separately. Don't want this patch to blow up more.
The test looks fine except for the 1second sleep. I can see that causing issues
on VMs but let's see.
Checking this in.
> 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)
