In the console of fully managed Flink, you can suspend or cancel a job that is in the RUNNING state. This topic describes how to suspend and cancel a job.
Background information
The suspend and cancel operations have different feature descriptions and use scenarios,
and correspond to different job restart policies. You can choose the appropriate operation
for your scenario. The following table describes the differences between the two operations.
Operation | Description | Scenario | Job restart policy |
---|---|---|---|
Suspend | If a job is suspended, the system creates a savepoint for the job and cancels the job. | If you modify the resource configuration, the configuration takes effect after the job is suspended and then restarted. | By default, when you start the job, the job resumes from the latest state. For more information, see Start a job. |
Cancel | If a job is canceled, the system clears the checkpoint information about the job. | If you modify the SQL logic, change the job version, add or delete parameters to or from the WITH clause, or add parameters for a job, the changes take effect after you cancel the job and then restart it. | If you restart a job that is canceled, 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. For more information, see Start a job.
Note If the state of the savepoint that is used to resume the job is not supported because
you modify the job configurations, such as changing the SQL logic, the job can only
be started without state.
|
Suspend a job
- Log on to the Realtime Compute for Apache Flink console.
- On the Fully Managed Flink tab, find the workspace that you want to manage and click Console in the Actions column.
- In the left-side navigation pane, click Deployments.
- On the Deployments page, find the job that you want to suspend and click Suspend in the Actions column.
- Click OK.