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 Thu, 09 Jul 2015 14:24:04 GMT

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

ASF GitHub Bot commented on FLINK-2288:

Github user mxm commented on the pull request:

    Yes that makes sense. So the user will always have to connect to the web interface of
the leading job manager, right? We could only circumvent that by separating the web interface
from the job manager.

> 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

View raw message