Flink Application States

This reference lists the actions available on a Flink application, the states a Flink application can hold, and the mapping between the Flink job status and the status shown on the Application card.

Type

Reference

Goal

Look up the actions, states, and status conditions of a Flink application.

Audience

An Application owner who can start and stop a Flink application in Self-Service.

When to use

When you need to interpret the state shown on a Flink Application card or check which action a state allows.

Contents

The sections below cover each area in this reference:

Available application actions

The following actions are available to the Application owner. The Platform Manager polls the Flink job status and displays the current state on the Application card.

Application action Effect

START

Starts the Flink job with no state restored from a previous run. Available in the Undeployed state once the application’s SQL has been saved.

STOP

Cancels the Flink job. Available in the Starting, Running, and Failing states.

RESUME

Starts the Flink job from its latest state. Available in the Stopped and Failed states.

RESET

Returns the application to Undeployed, so the next START runs the Flink job with no state restored. Available in the Stopped and Failed states.

No action is available in the Stopping state.

State lifecycle

A Flink application transitions through states based on the Flink job status and user actions. The Platform Manager polls the status and displays the current state on the Application card. The following table lists the transitions between states.

From state Trigger To state

Undeployed

START action; the Flink job is provisioned

Starting

Starting or Failing

The Flink job reports status RUNNING

Running

Running

The Flink job reports status RESTARTING or FAILING, or keeps restarting while reporting RUNNING

Failing

Starting, Running, or Failing

The Flink job reports status FAILED, or reports a failure

Failed

Starting, Running, or Failing

STOP action; the Flink job is cancelled

Stopping

Stopping

The Flink job reports status CANCELLED, TERMINATED, or SUSPENDED

Stopped

Running

The Flink job reports status FINISHED

Undeployed

Stopped or Failed

RESUME action; the Flink job starts from its latest state

Starting

Stopped or Failed

RESET action

Undeployed

The following diagram shows the same lifecycle.

figure

Status mapping

Self-Service polls the Platform Manager for the Flink job status while the Application Overview page is open. The status shown on the Application card is one of the following.

Status Flink status Condition

Undeployed

(no job), CANCELLED, TERMINATED, SUSPENDED, FINISHED

No Flink job is running and the application wasn’t stopped with STOP. This is the initial state before the first START, and the state after RESET.

Starting

CREATED, STARTING

The Flink job is being provisioned; it hasn’t yet reported RUNNING.

Running

RUNNING, STANDBY

The Flink job is active and processing data.

Failing

RESTARTING, FAILING, or RUNNING while the job keeps restarting

The Flink job is restarting after a failure. Use Viewing Application Logs to investigate.

Failed

FAILED, or any status that reports a failure while the application isn’t Failing or Stopping

The Flink job has failed. Use Viewing Application Logs to investigate, then RESUME or RESET.

Stopping

CANCELLING, TERMINATING

The Flink job is being cancelled.

Stopped

CANCELLED, TERMINATED, SUSPENDED, FINISHED

The application was stopped with STOP and the Flink job is no longer running. It can be resumed or reset.

Unknown

Any other status

The Platform Manager doesn’t recognise the Flink job status. No action is available.