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/12/22 13:56:00 UTC

[jira] [Closed] (FLINK-11719) Remove JobMaster#start(JobMasterId) and #suspend

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

Till Rohrmann closed FLINK-11719.
---------------------------------
    Fix Version/s: 1.13.0
       Resolution: Fixed

Fixed via

5fc355e0f7d9e74824b247d71f89056530cce5b4
a2b04fb7331aac1b18e59b58cd256b0368d9ce70
95d5bd5c86f0953d6f1674afc2609fa5b5093adb
f10227425d0db2e892fee6a446ed241a65d7dad5
c7084b3b5fc24be9aa557e8626e9bafb02302f05

> Remove JobMaster#start(JobMasterId) and #suspend
> ------------------------------------------------
>
>                 Key: FLINK-11719
>                 URL: https://issues.apache.org/jira/browse/FLINK-11719
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.8.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.13.0
>
>
> Currently, the {{JobMaster}} contains a lot of mutable state which is necessary because it is used across different leadership sessions by the {{JobManagerRunner}}. For this purpose, we have the methods {{JobMaster#start(JobMasterId)}} and {{#suspend}}. The mutable state management makes things on the {{JobMaster}} side more complicated than they need to be. In order to improve the {{JobMaster's}} maintainability I suggest to remove this logic and instead terminate the {{JobMaster}} if the {{JobManagerRunner}} loses leadership. This entails that for every leadership we will create a new {{JobMaster}} instance.



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