After you create and publish a job, you must start the job on the Developments page to run the job. If you want to resume a job that is suspended or stopped, you must start the job.

Background information

You can start a job in the following scenarios:
  • Start a job that is published: You can select Start without state for Start Method and specify Start Time for Reading Data.
  • Start a job that is suspended: If a job is suspended, the system automatically runs savepoints once and terminates the job. By default, if you start a job that is suspended, the job resumes from the latest state. You can also specify Start Time for Reading Data.
  • Start a job that is stopped: If a job is stopped, the system automatically clears the checkpoint information about the job. If you start a job that is stopped, you can select Start without state for Start Method and specify Start Time for Reading Data. You can also resume a job from the savepoint that you select.

Procedure

  1. Log on to the Realtime Compute for Apache Flink console.
  2. On the Fully Managed Flink tab, find the workspace that you want to manage, and click Console in the Actions column.
  3. In the left-side navigation pane, choose Applications > Deployments.
  4. Find the job that you want to start, and click Start in the Actions column.
  5. In the Deployment Starting Configuration dialog box, configure Start Method and Start Options.
    Deployment Starting Configuration dialog box in different scenarios:
    • Start a job that is publishedStart a job that is published
    • Start a job that is suspendedStart a job that is suspended
    • Start a job that is stoppedStart a new job or a job that is stopped
  6. Click Confirm Running.
  7. View the change of the job status.
    After you click Start, you can view the transition process from a current state to a desired state and the final result. Status changeThe following table describes the meaning of each job state.
    • Desired states
      State Description
      RUNNING The job is running normally.
      SUSPENDED The job is suspended.
      CANCELLED The job is stopped.
    • Current states
      State Description
      RUNNING The job is running normally.
      CANCELLED The job is stopped.
      SUSPENDED The job is suspended.
      FINISHED The job is completed.
      TRANSITIONING The job is being transitioned to a desired state.
      FAILED The job status fails to be transitioned to the desired state. Manual processing is required.
      ClusterUnreachable Ververica Platform (VVP) fails to access JobManager to obtain the job status.