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-6174) Introduce a leader election service in yarn mode to make JobManager always available
Date Mon, 08 May 2017 18:46:04 GMT

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

ASF GitHub Bot commented on FLINK-6174:

Github user StephanEwen commented on a diff in the pull request:

    --- Diff: flink-shaded-curator/flink-shaded-curator-recipes/pom.xml ---
    @@ -70,6 +70,15 @@ under the License.
    +							<relocations>
    --- End diff --
    Do we need this here? I think relocation happens in `flink-runtime`, when it puts curator
into its shaded jar.

> Introduce a leader election service in yarn mode to make JobManager always available
> ------------------------------------------------------------------------------------
>                 Key: FLINK-6174
>                 URL: https://issues.apache.org/jira/browse/FLINK-6174
>             Project: Flink
>          Issue Type: Sub-task
>          Components: JobManager
>            Reporter: Tao Wang
>            Assignee: Tao Wang
> Now in yarn mode, if we use zookeeper as high availability choice, it will create a election
service to get a leader depending on zookeeper election.
> When zookeeper leader crashes or the connection between JobManager and zookeeper instance
was broken, JobManager's leadership will be revoked and send a Disconnect message to TaskManager,
which will cancle all running tasks and make them waiting connection rebuild between JM and
> In yarn mode, we have one and only JobManager(AM) in same time, and it should be alwasy
leader instead of elected through zookeeper. We can introduce a new leader election service
in yarn mode to achive that.

This message was sent by Atlassian JIRA

View raw message