Sign inTry Free

Rolling Restart in a Cluster

You can do a rolling restart of your cluster, where you keep your cluster up and running throughout the process via HA. To avoid loss of data, actions like rolling restart or removal of a leaf require more than just stopping and restarting the nodes. The following commands should be used.

To shut down a node:

Note: The sdb-admin stop-node command will display this query:

Continue to stop the node(s) without taking a database snapshot?

Enter 'n' at the prompt.

To restart a node:

Restart the nodes in any order and combination, ensuring all the time, you have enough nodes up to keep the cluster running. This implies only shutting down nodes in one availability group at a time, and keeping enough availability groups up to serve the workload.

If you frequently need to stop all nodes on one host it is advisable to use the load-balanced mode of HA.

In case you do not plan to attach a leaf back again, then the REBALANCE PARTITIONS command should be used.

Last modified: June 22, 2022

Was this article helpful?

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