Sign inTry Free

Suspend and Resume a Flow Instance

On this page

Suspend a Flow instance to stop its compute without deleting its configuration or persistent state. A suspended Flow instance can be resumed later. Temporary working storage is released when the instance is suspended and recreated when it is resumed.

Flow Instance States

State

Description

Running

The Flow instance is active. 

Suspending

The Flow instance is transitioning to the Suspended state.

Suspended

The Flow instance's compute is stopped. Its configuration and persistent state are retained, and it can be resumed.

Resuming

The Flow instance is transitioning back to the Running state.

Suspending and Resuming are transitional states.

Suspend a Flow Instance

  1. In the Cloud Portal, navigate to Ingestion > Flow.

  2. In the Actions column for the Flow instance, click the three dots (…).

  3. Select Suspend.

  4. In the confirmation dialog, select Suspend.

The instance transitions through Suspending to Suspended.

Resume a Flow Instance

  1. In the Cloud Portal, navigate to Ingestion > Flow.

  2. In the Actions column for the instance, click the three dots (…).

  3. Select Resume.

  4. In the confirmation dialog, select Resume. 

When a Flow instance is resumed, it transitions through Resuming to Running. After the instance returns to Running, confirm that ingestion is progressing on the Logs tab of the Flow dashboard.

Note: Ingestion may not restart from the exact point at which the Flow instance was suspended. Monitor the Logs tab after resuming to confirm the ingestion progress.

Suspend and Resume a Cluster

When you suspend a cluster:

  • Running Flow instances are automatically suspended.

  • Flow instances are not displayed in the Flow list while the cluster is suspended.

When you resume the cluster:

  • Flowinstances automatically suspended by the cluster operation resume automatically.

  • Flow instances that were suspended manually before the cluster suspension remain suspended.

  • The Flow list displays all instances again.

Billing Impact

While a Flow instance is Suspended, its compute is not billed.

Last modified:

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In