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/07/16 02:23:00 UTC
[jira] [Commented] (FLINK-11843) Dispatcher fails to recover jobs
if leader change happens during JobManagerRunner termination
[ https://issues.apache.org/jira/browse/FLINK-11843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885782#comment-16885782 ]
Till Rohrmann commented on FLINK-11843:
---------------------------------------
Made this a critial issue for 1.9.0 [~tzulitai], [~ykt836]. Let's see whether we can fix it for the upcoming release.
> 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
> Fix For: 1.9.0, 1.10.0
>
>
> 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
(v7.6.14#76016)