[ 
https://issues.apache.org/jira/browse/YARN-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144550#comment-14144550
 ] 

Rohith commented on YARN-2579:
------------------------------

For fixing this, approaches I can think of are
1. we can call ((Service) rmDispatcher).stop(); in separate thread, so current 
lock on transitionToStandby() will be released and RMFatalEventDispatcher holds 
the lock. By this time, RM state already in standby state.

2. Instead of resetting new async diapatcher, let maintain single dispatcher 
for period of jvm life. There should mechanism for clearing queued events in 
diapatcher, so dispatcher should not process .

3. Set separate dispatcher thread for all RMStateStore events.

Please suggest your opinion this bug fix.

> Both RM's state is Active , but 1 RM is not really active.
> ----------------------------------------------------------
>
>                 Key: YARN-2579
>                 URL: https://issues.apache.org/jira/browse/YARN-2579
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.5.1
>            Reporter: Rohith
>            Assignee: Rohith
>
> I encountered a situaltion where both RM's web page was able to access and 
> its state displayed as Active. But One of the RM's ActiveServices were 
> stopped.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to