You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Kurt Young (JIRA)" <ji...@apache.org> on 2016/09/21 14:53:20 UTC

[jira] [Updated] (FLINK-4657) Implement HighAvailabilityServices based on zookeeper

     [ https://issues.apache.org/jira/browse/FLINK-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt Young updated FLINK-4657:
------------------------------
    Description: 
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

  was:
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}


> 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)