[
https://issues.apache.org/jira/browse/FLINK-33483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Pohl closed FLINK-33483.
---------------------------------
Resolution: Cannot Reproduce
Based on your comment in FLINK-12302 it appears that the issue doesn't exist in
newer versions of Flink (you mentioned 1.16). As stated in [my
comment|https://issues.apache.org/jira/browse/FLINK-12302?focusedCommentId=17785444&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17785444]
in the very same issue, doing code investigations in old versions like 1.12
are quite tedious. The community agreed on supporting the two most-recently
released versions (i.e. 1.18 and 1.17 for now). Upgrading Flink to a more
recent version might be the best thing to do here as it comes with multiple
other bugfixes.
I'm hesitating to pick this one up as an issue as it's 1.12-related. I'm gonna
close this issue. Feel free to reopen it if you have additional information or
you disagree.
> 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: Deployment / YARN
> Affects Versions: 1.12.2
> Reporter: Xin Chen
> Priority: Major
> Attachments: container_e15_1693914709123_8498_01_000001_8042,
> reproduce.log
>
>
> 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)
