[ https://issues.apache.org/jira/browse/FLINK-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15552151#comment-15552151 ]
ASF GitHub Bot commented on FLINK-4657: --------------------------------------- Github user StephanEwen commented on the issue: https://github.com/apache/flink/pull/2550 @KurtYoung Yes, the `cluster-id` should lake the role of `availability.zookeeper.path.namespace` - in some sense it is a renaming. I would also suggest we use existing IDs where possible - for example the Yarn application ID. That will make it easier for users who debug to correlate the ZooKeeper entries with Flink jobs. > 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)