You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/10/26 06:50:00 UTC

[jira] [Updated] (FLINK-19806) Job may try to leave SUSPENDED state in ExecutionGraph#failJob()

     [ https://issues.apache.org/jira/browse/FLINK-19806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-19806:
-----------------------------------
    Labels: pull-request-available  (was: )

> Job may try to leave SUSPENDED state in ExecutionGraph#failJob()
> ----------------------------------------------------------------
>
>                 Key: FLINK-19806
>                 URL: https://issues.apache.org/jira/browse/FLINK-19806
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Zhu Zhu
>            Assignee: Zhu Zhu
>            Priority: Major
>              Labels: pull-request-available
>
> {{SUSPENDED}} is a terminal state which a job is not supposed to leave this state once entering. However, {{ExecutionGraph#failJob()}} did not check it and may try to transition a job out from {{SUSPENDED}} state. This will cause unexpected errors and may lead to JM crash.
> The problem can be visible if we rework {{ExecutionGraphSuspendTest}} to be based on {{DefaultScheduler}}.
> We should harden the check in {{ExecutionGraph#failJob()}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)