flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Metzger (Jira)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-20382) Exception thrown from JobMaster.startScheduling() may be ignored.
Date Mon, 30 Nov 2020 13:14:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240760#comment-17240760

Robert Metzger commented on FLINK-20382:

Thanks for the quick fix! I agree that failing hard is a good short-term fix.

But from a user's perspective, I would not expect my JobManager to exit if I submit a custom
source implementation that throws an exception. [I guess failing the job with the exception|https://github.com/apache/flink/pull/14251#discussion_r531639026]
thrown by the operator coordinator would be the expected behavior.
[~sewen] Can you take a look at his?

> 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

View raw message