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

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 1.12.2
• Component/s: Deployment / YARN
• Assignee: Unassigned
• Reporter: Xin Chen
• Created: 08/Nov/23 11:40
• Updated: 14/Nov/23 09:09
• Resolved: 13/Nov/23 10:07

Description

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?