flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-4657) Implement HighAvailabilityServices based on zookeeper
Date Mon, 03 Oct 2016 20:40:20 GMT

     [ https://issues.apache.org/jira/browse/FLINK-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Till Rohrmann resolved FLINK-4657.
----------------------------------
    Resolution: Fixed

Added via f7cfc1bb66affab43bb9e2643d48ac5bfc28fe3e

> Implement HighAvailabilityServices based on zookeeper
> -----------------------------------------------------
>
>                 Key: FLINK-4657
>                 URL: https://issues.apache.org/jira/browse/FLINK-4657
>             Project: Flink
>          Issue Type: New Feature
>          Components: Cluster Management
>            Reporter: Kurt Young
>            Assignee: Kurt Young
>
> For flip-6, we will have ResourceManager and every JobManager as potential leader contender
and retriever. We should separate them by using different zookeeper path. 
> For example, the path could be /leader/resource-manaeger for RM. And for each JM, the
path could be /leader/job-managers/JobID



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

Mime
View raw message