[
https://issues.apache.org/jira/browse/YARN-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189195#comment-14189195
]
Karthik Kambatla commented on YARN-2579:
----------------------------------------
Thanks, [~rohithsharma]. Looking at the tests and your explanation, I think I
see what you are saying.
However, looking into the code, I am not convinced it is draining out that is
causing this issue. {{rmDispatcher}} is an {{AsyncDispatcher}}, with
{{drainEventsOnStop}} always false. So, {{rmDispatcher.stop()}} shouldn't lead
to any draining of events. I noticed a couple of other issues in the
AsyncDispatcher code:
# {{eventHandlerThread.join}} in serviceStop should take a timeout as well
# {{dispatch(event)}} in AsyncDispatcher#createThread doesn't have a try-catch
block
With the current patch, I wonder if there are any unexpected side-effects.
> 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
> Attachments: YARN-2579.patch, YARN-2579.patch
>
>
> 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)
