[
https://issues.apache.org/jira/browse/YARN-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853076#comment-13853076
]
Karthik Kambatla commented on YARN-1029:
----------------------------------------
Spoke to Bikas offline.
Bikas thinks we are trying to do too many things in this JIRA and it would be
good to cut the scope down and create follow up JIRAs for the remaining items.
With all the confusion created by the various items, I agree with him. The
proposal is to capture only the following in this JIRA:
# When automatic embedded failover is enabled (two configs), start the
RMZKActiveStandbyElector (embedded leader election).
# Unify the zookeeper connection related configs (timeouts, ACLs, etc.) between
the embedded election and zk-store.
# Address only automatic failover (if an Active RM goes down, the other RM
takes over as Active).
Follow-up items (will create separate JIRAs for these):
# Manual graceful failover (yarn rmadmin -failover rm1 rm2) - we might not want
to support it in the first place when automatic failover is enabled. Users can
forcefully failover (transition to standby, followed by transition to active)
# Simplify the configuration - IOW, use a single config to turn on both ZK
store and embedded leader election.
> 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)
