[
https://issues.apache.org/jira/browse/FLINK-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243387#comment-17243387
]
Till Rohrmann commented on FLINK-20382:
---------------------------------------
Yes, the code is currently not written with the assumption that
{{startScheduling}} can fail and, hence, is lacking a retry. If we want to
tolerate {{startScheduling}} failures, then we need to change this.
> Exception thrown from JobMaster.startScheduling() may be ignored.
> -----------------------------------------------------------------
>
> Key: FLINK-20382
> URL: https://issues.apache.org/jira/browse/FLINK-20382
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.11.2
> Reporter: Jiangjie Qin
> Assignee: Till Rohrmann
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.12.0, 1.11.3
>
>
> Currently {{JobMaster.resetAndStartScheduler()}} invokes
> {{startScheduling()}} in a {{thenRun}} clause without {{exceptionally}} or
> {{handle}} to handle exceptions. The job may hang if an exception is thrown
> when starting scheduling, e.g. failed to create operator coordinators.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
