[
https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865773#comment-13865773
]
Karthik Kambatla commented on YARN-1574:
----------------------------------------
Good catch, [~xgong]. I see two ways of handling this.
# Add a way to unregister handlers from the dispatcher. Might be a very
involved approach.
# Add a method resetDispatcher that creates a new Dispatcher, adds RMFatalEvent
handler to it, inits and starts it, and finally sets rmDispatcher to that. This
method can then be called as the last step of RM#transitionToStandby.
> When RM transit from Active to Standby, the same eventDispatcher should not
> be registered more than once
> --------------------------------------------------------------------------------------------------------
>
> Key: YARN-1574
> URL: https://issues.apache.org/jira/browse/YARN-1574
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Xuan Gong
> Assignee: Xuan Gong
> Priority: Blocker
>
> Currently, we move rmDispatcher out of ActiveService. But we still register
> the Event dispatcher, such as schedulerDispatcher, RMAppEventDispatcher when
> we initiate the ActiveService.
> Almost every time when we transit RM from Active to Standby, we need to
> initiate the ActiveService. That means we will register the same event
> Dispatcher which will cause the same event will be handled several times.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
