Overview

On the Job Management page of Flink jobs, you can submit a Flink job. Currently, the following job types are supported:

  • Flink SQL uses SQL statements to define jobs and can be submitted to any general purpose queue.

  • Flink Jar customizes a JAR package job based on Flink APIs. It runs on dedicated queues.

Flink job management provides the following functions:

Flink Jobs Page

On the Overview page, click Flink Jobs to go to the Flink job management page. Alternatively, you can choose Job Management > Flink Jobs from the navigation pane on the left. The page displays all Flink jobs. If there are a large number of jobs, they will be displayed on multiple pages. DLI allows you to view jobs in all statuses.

Table 1 Job management parameters

Parameter

Description

ID

ID of a submitted Flink job, which is generated by the system by default.

Name

Name of the submitted Flink job.

Type

Type of the submitted Flink job. Including:

  • Flink SQL: Flink SQL jobs

  • Flink Jar: Flink Jar jobs

Status

Job statuses, including:

  • Draft

  • Submitting

  • Submission failed

  • Running: After the job is submitted, a normal result is returned.

  • Running exception: The job stops running due to an exception.

  • Downloading

  • Idle

  • Stopping

  • Stopped

  • Stopping failed

  • Creating the savepoint

  • Completed

Description

Description of the submitted Flink job.

Username

Name of the user who submits a job.

Created

Time when a job is created.

Started

Time when a Flink job starts to run.

Duration

Time consumed by job running.

Operation

  • Edit: Edit a created job. For details, see Editing a Job.

  • Start: Start and run a job. For details, see Starting a Job.

  • More

    • FlinkUI: After you click this button, the Flink job execution page is displayed.

      Note

      When you execute a job on a created queue, the cluster is restarted. It takes about 10 minutes. If you click FlinkUI before the cluster is created, an empty projectID will be cached. The FlinkUI page cannot be displayed.

      You are advised to use a dedicated queue so that the cluster will not be released. Alternatively, wait for a while after the job is submitted (the cluster is created), and then check FlinkUI.

    • Stop: Stop a Flink job. If this function is unavailable, jobs in the current status cannot be stopped.

    • Delete: Delete a job.

      Note

      A deleted job cannot be restored.

    • Modify Name and Description: You can modify the name and description of a job. For details, see Modifying Name and Description.

    • Import Savepoint: Import the data exported from the original CS job. For details, see Importing to a Savepoint.

    • Trigger Savepoint: You can click this button for jobs in the Running status to save the job status. For details, see Triggering a Savepoint.

    • Permissions: You can view the user permissions corresponding to the job and grant permissions to other users. For details, see Managing Flink Job Permissions.

    • Runtime Configuration: You can enable Alarm Generation upon Job Exception and Auto Restart upon Exception. For details, see Runtime Configuration.

last updated: 2024-12-10 15:25 UTC - commit: 9e0ebe18fe0b43010decd2c132af9f5362beb29e