You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Bertrand Bossy (JIRA)" <ji...@apache.org> on 2018/02/28 04:18:00 UTC

[jira] [Commented] (FLINK-7470) Acquire RM leadership before registering with Mesos

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

Bertrand Bossy commented on FLINK-7470:
---------------------------------------

Is there any update on this? FLIP-6 mode for Mesos seems to have severe issues due to that.

> Acquire RM leadership before registering with Mesos
> ---------------------------------------------------
>
>                 Key: FLINK-7470
>                 URL: https://issues.apache.org/jira/browse/FLINK-7470
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Mesos
>            Reporter: Eron Wright 
>            Priority: Major
>
> Mesos doesn't support fencing tokens in the scheduler protocol; it assumes external leader election among scheduler instances.   The last connection wins; prior connections for a given framework ID are closed.
> The Mesos RM should not register as a framework until it has acquired RM leadership.   Evolve the ResourceManager as necessary.   One option is to introduce an ResourceManagerRunner that acquires leadership before starting the RM.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)