Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-33483

Why is “UNDEFINED” defined in the Flink task status?

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Cannot Reproduce
    • 1.12.2
    • None
    • Deployment / YARN
    • None

    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?

      Attachments

        1. container_e15_1693914709123_8498_01_000001_8042
          80 kB
          Xin Chen
        2. reproduce.log
          129 kB
          Xin Chen

        Activity

          People

            Unassigned Unassigned
            xinchen147 Xin Chen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: