You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/10/11 16:42:00 UTC

[jira] [Closed] (FLINK-19555) Remove runAsyncWithoutFencing from MesosResourceManager

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

Till Rohrmann closed FLINK-19555.
---------------------------------
    Resolution: Fixed

Fixed via bfd85fdb76b672fc519cfe635e3334316be9d42d

> Remove runAsyncWithoutFencing from MesosResourceManager
> -------------------------------------------------------
>
>                 Key: FLINK-19555
>                 URL: https://issues.apache.org/jira/browse/FLINK-19555
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Mesos, Runtime / Coordination
>    Affects Versions: 1.12.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.12.0
>
>
> With FLINK-9936 we introduced that the {{MesosResourceManager}} can process {{Disconnected}} messages also if the {{MesosResourceManager}} is not the leader. Since we are re-creating the monitors and coordinators in case of a new leader session. I believe that this call is no longer necessary. Hence, I propose to remove it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)