[
https://issues.apache.org/jira/browse/YARN-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851977#comment-13851977
]
Karthik Kambatla commented on YARN-1029:
----------------------------------------
I am a little confused here - I am not sure if we have consensus on whether the
patch posted here is in the right direction and I should go ahead and
incorporate comments to improve it (unify zk configs, automatically set leader
election configs) or if we would want to change the fundamental approach of
addressing this.
Current patch summary:
# RM starts a service, RMZKActiveStandbyElector, when automatic failover is
enabled and configured to be embedded.
# RMZKActiveStandbyElector spawns a thread that participates in leader election
through the ActiveStandbyElector
# RMZKActiveStandbyElector implements ElectorCallBacks for transitioning the RM
to active, standby.
# AdminService and RMZKActiveStandbyElector implement ZKFCProtocol (a.ka.
GracefulFailoverProtocol) for graceful failover through "yarn rmadmin -failover
rm1 rm2" (HAAdmin)
# TestRMFailover verifies both automatic failover and manual graceful failover
> Allow embedding leader election into the RM
> -------------------------------------------
>
> Key: YARN-1029
> URL: https://issues.apache.org/jira/browse/YARN-1029
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Karthik Kambatla
> Attachments: embedded-zkfc-approach.patch, yarn-1029-0.patch,
> yarn-1029-0.patch, yarn-1029-approach.patch
>
>
> It should be possible to embed common ActiveStandyElector into the RM such
> that ZooKeeper based leader election and notification is in-built. In
> conjunction with a ZK state store, this configuration will be a simple
> deployment option.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
