Return-Path: X-Original-To: apmail-flink-issues-archive@minotaur.apache.org Delivered-To: apmail-flink-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 78BCC18675 for ; Mon, 29 Jun 2015 09:00:09 +0000 (UTC) Received: (qmail 25754 invoked by uid 500); 29 Jun 2015 09:00:09 -0000 Delivered-To: apmail-flink-issues-archive@flink.apache.org Received: (qmail 25717 invoked by uid 500); 29 Jun 2015 09:00:09 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 25697 invoked by uid 99); 29 Jun 2015 09:00:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Jun 2015 09:00:09 +0000 Date: Mon, 29 Jun 2015 09:00:09 +0000 (UTC) From: "Ufuk Celebi (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FLINK-2289) Make JobManager highly available MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLINK-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605308#comment-14605308 ] Ufuk Celebi commented on FLINK-2289: ------------------------------------ Issue creation race... ;) Can you copy your text to FLINK-2287? > Make JobManager highly available > -------------------------------- > > Key: FLINK-2289 > URL: https://issues.apache.org/jira/browse/FLINK-2289 > Project: Flink > Issue Type: Improvement > Reporter: Till Rohrmann > Assignee: Till Rohrmann > > Currently, the {{JobManager}} is the single point of failure in the Flink system. If it fails, then your job cannot be recovered and the Flink cluster is no longer able to receive new jobs. > Therefore, it is crucial to make the {{JobManager}} fault tolerant so that the Flink cluster can recover from failed {{JobManager}}. As a first step towards this goal, I propose to make the {{JobManager}} highly available by starting multiple instances and using Apache ZooKeeper to elect a leader. The leader is responsible for the execution of the Flink job. > In case that the {{JobManager}} dies, one of the other running {{JobManager}} will be elected as the leader and take over the role of the leader. The {{Client}} and the {{TaskManager}} will automatically detect the new {{JobManager}} by querying the ZooKeeper cluster. > Note that this does not achieve full fault tolerance for the {{JobManager}} but it allows the cluster to recover from failed {{JobManager}}. The design of high-availability for the {{JobManager}} is tracked in the wiki here [1]. > Resources: > [1] [https://cwiki.apache.org/confluence/display/FLINK/JobManager+High+Availability] -- This message was sent by Atlassian JIRA (v6.3.4#6332)