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 2019/02/21 16:01:00 UTC

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

Till Rohrmann created FLINK-11719:
-------------------------------------

             Summary: Remove JobMaster#start(JobMasterId) and #suspend
                 Key: FLINK-11719
                 URL: https://issues.apache.org/jira/browse/FLINK-11719
             Project: Flink
          Issue Type: Improvement
          Components: Distributed Coordination
    Affects Versions: 1.8.0
            Reporter: Till Rohrmann
            Assignee: Till Rohrmann


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
(v7.6.3#76005)