[
https://issues.apache.org/jira/browse/FLINK-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-20033.
---------------------------------
Fix Version/s: 1.12.0
Resolution: Fixed
Fixed via
1.12.0:
03047a78b6ad8017eb240548a009424d68ffc971
86a96c7909a1c1db35157ebec4164529c0290c7d
1.11.3:
90fb07c311aa6c91ad544705ee96a14ab9302122
32e23052af547bb1b99274778c666f3d814201a8
1.10.3:
9840907ec8c16d4d50d92388b883b959cc10f793
10bfd2971dd960ac799ba02156683fc7a740383d
> 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)
