[ https://issues.apache.org/jira/browse/FLINK-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618497#comment-14618497 ]
ASF GitHub Bot commented on FLINK-2288: --------------------------------------- Github user StephanEwen commented on the pull request: https://github.com/apache/flink/pull/886#issuecomment-119553437 We need to find a solution for the webfrontend, though. Starting it on random ports is not a real solution. Also the user that wants to see progress needs to connect manually to the web server of the leader JobManager. > 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)