Xin Chen created FLINK-33483:
--------------------------------
Summary: 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
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)
