[
https://issues.apache.org/jira/browse/FLINK-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-20033.
---------------------------------
Resolution: Fixed
Reverted the test and the change which makes the {{JobMaster.jobStatusChanged}}
call synchronous because of FLINK-20065. The actual fix introduced with
FLINK-19237 has not been reverted.
1.12.0:
dea47d6b17fdd26920c1bfbb5aea24a7003a16be
89262012a86647ebc3658027e5690a242b2f0782
1.11.3:
dcbf474343a43370ae08665e71dad708c65369ca
68d16f0f04b7ddf0ed5f7aadb14092c101a811f5
1.10.3:
d8fa676412a85d5e369e6367978ccfa8a7e07194
fef13fda361e6dfc566553316fcc8ca4943af787
> Job fails when stopping JobMaster
> ---------------------------------
>
> Key: FLINK-20033
> URL: https://issues.apache.org/jira/browse/FLINK-20033
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.10.2, 1.11.2
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.12.0, 1.10.3, 1.11.3
>
>
> When a {{JobMaster}} is stopped, we first disconnect all {{TaskExecutors}}.
> This disconnection causes potentially running {{Executions}} to fail. This in
> turn can cause a restart of the job or in the worst case a transition into
> {{FAILED}} state if the restarts are depleted. This again can cause the clean
> up of HA data.
> Instead of failing the job, the job should be suspended if the {{JobMaster}}
> gets stopped because this happens if the {{Dispatcher}} loses its leadership.
> The problem has been fixed unintentionally by FLINK-19237 in the master
> branch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
