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

Posted to issues@flink.apache.org by "Xin Chen (Jira)" <ji...@apache.org> on 2023/11/08 11:58:00 UTC

[jira] [Updated] (FLINK-33483) Why is “UNDEFINED” defined in the Flink task status?

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

Xin Chen updated FLINK-33483:
-----------------------------
    Attachment: container_e15_1693914709123_8498_01_000001_8042

> Why is “UNDEFINED” defined in the Flink task status?
> ----------------------------------------------------
>
>                 Key: FLINK-33483
>                 URL: https://issues.apache.org/jira/browse/FLINK-33483
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / RPC, Runtime / Task
>    Affects Versions: 1.12.2
>            Reporter: Xin Chen
>            Priority: Major
>         Attachments: container_e15_1693914709123_8498_01_000001_8042
>
>
> In the Flink on Yarn mode, if an unknown status appears in the Flink log, jm(jobmanager) will report the task status as undefined. The Yarn page will display the state as FINISHED, but the final status is *UNDEFINED*. In terms of business, it is unknown whether the task has failed or succeeded, and whether to retry. It has a certain impact. Why should we design UNDEFINED? Usually, this situation occurs due to zk(zookeeper) disconnection or jm abnormality, etc. Since the abnormality is present, why not use FAILED?
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)