After you develop a draft and deploy the draft as a deployment, you must start the deployment on the Deployments page to run the deployment. If you want to resume a deployment that is canceled, you also need to start the deployment. This topic describes how to start a streaming deployment and a batch deployment of the SQL type.

Prerequisites

If you want to allow other Alibaba Cloud accounts or RAM users to use your resources in fully managed Flink, you must grant them the required permissions, such as the permissions to start a deployment. For more information, see Assign a role to an Alibaba Cloud account, Grant permissions to a RAM user, Grant permissions to an account.

Limits

  • Only Realtime Compute for Apache Flink that uses Ververica Runtime (VVR) 4.0.11 or later supports the state data compatibility check.
  • Only the Log Service and Message Queue for Apache Kafka source table connectors allow you to configure the Specify source's start time (SLS/Kafka) parameter in the Start Job dialog box.
    The Specify source's start time (SLS/Kafka) parameter that is configured in the Start Job dialog box takes precedence over the startTime parameter that is configured in the DDL code of a draft. If you configure the Specify source's start time (SLS/Kafka) parameter in the Start Job dialog box and the startTime parameter in the DDL code, the configuration of the Specify source's start time (SLS/Kafka) parameter takes effect.
    Note
    • Not all connector types support the startTime parameter. For more information about whether the parameters in the WITH clause for each type of connector include the startTime parameter, see the related topic of the specific type of connector. For example, if you want to check whether the parameters in the WITH clause for a Log Service connector include the startTime parameter, see Parameters in the WITH clause for a Log Service connector.
    • The startTime parameter takes effect only if a new deployment is started and the startTime parameter is configured. If you start a deployment based on a checkpoint or savepoint, the startTime parameter does not take effect even if this parameter is configured.

You can specify startup options for only streaming deployments.

Precautions

If you select Latest State or Specific State when you start a deployment, the system performs a state data compatibility check. For more information about the state data compatibility check, see Reference for Flink state data compatibility.

Procedure

  1. Go to the Start Job dialog box.
    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, click Deployments.
    4. On the Deployments page, select STREAM or BATCH from the drop-down list of the deployment type.
      STREAM
  2. Find the desired deployment and click Start in the Actions column.
  3. In the Start Job dialog box, configure the startup options.
    You must configure the following startup options for streaming deployments:
    • Stateless: If you start a deployment for the first time without the need to reuse states, select this option. If a deployment cannot reuse a state, you can also select this option. If you select Stateless, you can select Specify source's start time (SLS/Kafka) to specify the start time for reading data.
    • Stateful: You can choose a specific startup strategy based on your business requirements.
      StrategyDescription
      Latest StateIf you want to resume a deployment from the latest state of a savepoint or a checkpoint, select this option. If you select this option to start your deployment, the system performs a state data compatibility check. For more information about the state data compatibility check, see Reference for Flink state data compatibility.
      Specific StateIf you want to resume a deployment from a savepoint of the current deployment, select this option. For more information about how to create a savepoint, see Status set management.
      Allow Non-restored StateBy default, fully managed Flink attempts to match all savepoints with the deployment that is being published. If the status of an operator changes due to the modification of the deployment, tasks of the deployment may not be restored. If you turn on this switch, fully managed Flink skips the states that do not match the deployment and allows the deployment to start. For more information about Allow Non-Restored State, see Allow None-Restored State.
  4. In the Start Job dialog box, click Start.
    On the Deployments page, view the deployment status.
    State typeStateDescription
    TransitioningSTARTINGThe deployment is being started.
    StableRUNNINGThe deployment is running.
    Note When a deployment is running, the system monitors the deployment and generates a health score for the deployment based on the monitoring results. The health score indicates the health status of the deployment. If the health score of the deployment is not 100, the deployment is at risk. In this case, you can click the score in the Health column for the deployment and view the specific risk causes and handling suggestions to restore the deployment. For more information about the deployment diagnostics feature, see Perform intelligent deployment diagnostics.
    CANCELLEDIf you click Cancel for a deployment in the Actions column, the deployment enters the CANCELLED state.
    FINISHEDAfter a batch deployment or a streaming deployment that triggers throttling is complete, the deployment enters the FINISHED state.
    FailedFAILEDThe deployment fails to run.