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-2288) Setup ZooKeeper for distributed coordination
Date Wed, 08 Jul 2015 12:10:05 GMT

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

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

Github user StephanEwen commented on the pull request:

    https://github.com/apache/flink/pull/886#issuecomment-119553291
  
    BTW: It is beautiful how easy it is to start multiple TaskManagers and JobManagers on
one machine now :-)


> Setup ZooKeeper for distributed coordination
> --------------------------------------------
>
>                 Key: FLINK-2288
>                 URL: https://issues.apache.org/jira/browse/FLINK-2288
>             Project: Flink
>          Issue Type: Sub-task
>          Components: JobManager, TaskManager
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>             Fix For: 0.10
>
>
> Having standby JM instances for job manager high availabilty requires distributed coordination
between JM, TM, and clients. For this, we will use ZooKeeper (ZK).
> Pros:
> - Proven solution (other projects use it for this as well)
> - Apache TLP with large community, docs, and library with required "recipies" like leader
election (see below)
> Related Wiki: https://cwiki.apache.org/confluence/display/FLINK/JobManager+High+Availability



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message