[
https://issues.apache.org/jira/browse/FLINK-11843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-11843.
---------------------------------
Resolution: Fixed
Fixed via
1c2097e716
32a3e5a6a0
035c6a1a2e
401f5f3970
7fcb64bf76
e3f202698f
06e79c8eb5
717b77c665
78583463e8
1f2969357c
cdd0c29102
a5438ca696
a805f1b299
c8675858f3
4e9dd7f788
a123c8f50a
2d3426f332
a17b9c0a3e
9bf06697a5
7851cb6966
c1f67ef1f2
c5dee3141c
7a23e02832
b6128ca6c8
8467acc100
cb5fba5bba
f67349db10
358d46c784
07c5b720fc
0b9382bb3b
90db87ddb9
9d447ada31
7956a14c4e
d734ac0bc6
637a6e9eae
431e2a0423
89e9b6f000
> Dispatcher fails to recover jobs if leader change happens during
> JobManagerRunner termination
> ---------------------------------------------------------------------------------------------
>
> Key: FLINK-11843
> URL: https://issues.apache.org/jira/browse/FLINK-11843
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.7.2, 1.8.0, 1.9.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{Dispatcher}} fails to recover jobs if a leader change happens during
> the {{JobManagerRunner}} termination of the previous run. The problem is that
> we schedule the start future of the recovered {{JobGraph}} using the
> {{MainThreadExecutor}} and additionally require that this future is completed
> before any other recovery operation from a subsequent leadership session is
> executed. If now the leadership changes, the {{MainThreadExecutor}} will be
> invalidated and the scheduled future will never be completed.
> The relevant ML thread:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/1-7-1-job-stuck-in-suspended-state-td26439.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
