Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Mon, 17 Oct 2016 12:48:58 +0000 (UTC)
From: "Stephan Ewen (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.13012705.1476648557000.3805.1476708538354@Atlassian.JIRA>
In-Reply-To: <JIRA.13012705.1476648557000@Atlassian.JIRA>
References: <JIRA.13012705.1476648557000@Atlassian.JIRA> <JIRA.13012705.1476648557863@arcas>
Subject: [jira] [Commented] (FLINK-4835) Implement standalone High
 Availability Services
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 17 Oct 2016 12:49:00 -0000


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

Stephan Ewen commented on FLINK-4835:
-------------------------------------

You are right, that is probably an artifact right now. I was only thinking of the {{ResourceManager}}, assuming it is in the same process as the {{JobManager(s)}}.

> Implement standalone High Availability Services
> -----------------------------------------------
>
>                 Key: FLINK-4835
>                 URL: https://issues.apache.org/jira/browse/FLINK-4835
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Cluster Management
>         Environment: FLIP-6 feature branch
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>
> This is a version of the {{HighAvailabilityServices}} that is in fact not highly available and used for setups where everything runs in one process (mini clusters) and simple setups (non-ha)


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