[
https://issues.apache.org/jira/browse/FLINK-11719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-11719:
-----------------------------------
Labels: pull-request-available (was: )
> 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
>
> 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)
