[
https://issues.apache.org/jira/browse/FLINK-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528274#comment-15528274
]
ASF GitHub Bot commented on FLINK-4657:
---------------------------------------
Github user KurtYoung commented on the issue:
https://github.com/apache/flink/pull/2550
For "cluster-id" thing, actually there is some similar functionality in
current Flink, configed by "high-availability.zookeeper.path.namespace". It
will work with another config "high-availability.zookeeper.path.root" which is
"/flink" by default.
The real root in zk will be "/flink/some_namespace", we can change the
namespace when we have a new cluster. Maybe we should do it explicitly in Cli
or some shell script. Do you think that will work?
> Implement HighAvailabilityServices based on zookeeper
> -----------------------------------------------------
>
> Key: FLINK-4657
> URL: https://issues.apache.org/jira/browse/FLINK-4657
> Project: Flink
> Issue Type: New Feature
> Components: Cluster Management
> Reporter: Kurt Young
> Assignee: Kurt Young
>
> For flip-6, we will have ResourceManager and every JobManager as potential
> leader contender and retriever. We should separate them by using different
> zookeeper path.
> For example, the path could be /leader/resource-manaeger for RM. And for each
> JM, the path could be /leader/job-managers/JobID
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
