flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4657) Implement HighAvailabilityServices based on zookeeper
Date Mon, 03 Oct 2016 20:41:20 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543367#comment-15543367
] 

ASF GitHub Bot commented on FLINK-4657:
---------------------------------------

Github user tillrohrmann commented on the issue:

    https://github.com/apache/flink/pull/2550
  
    Thanks for your contribution @KurtYoung. I've merged the code. You can close the PR now.


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

Mime
View raw message