[
https://issues.apache.org/jira/browse/YARN-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862110#comment-13862110
]
Vinod Kumar Vavilapalli commented on YARN-1029:
-----------------------------------------------
bq. We initially had it in the RM, but thought AdminService is a better place.
http://tinyurl.com/qdo2vos
Sure. It's not a big deal either ways. Let's leave it the way you had in the
latest patch. But the comment about using fields from RMContext holds.
bq. TestRMFailover needs it.
Hm.. then let's put it in server-common as a compile-time dependency and
specifically in hadop-yarn-client as a test-dependency. Okay?
bq. The elector doesn't explicitly fence [...]
May be state that somehow? It did confuse me a little.
bq. I am okay either way, but I think the fewer configs we force admins to set
the better. If there is a single cluster, it should be perfectly okay to just
use the default. No?
Yeah, thought about it. But it seemed to me that the problem of debugging bad
issues with conflicting cluster-ids is worse than the little convenience the
default value is bringing.
> 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-1.patch, yarn-1029-2.patch, yarn-1029-3.patch,
> yarn-1029-4.patch, yarn-1029-5.patch, yarn-1029-6.patch, yarn-1029-7.patch,
> yarn-1029-7.patch, yarn-1029-8.patch, yarn-1029-9.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.5#6160)
