Sign inTry Free

Warning

SingleStore 9.0 gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 8.9 is recommended for production workloads, which can later be upgraded to SingleStore 9.0.

Uninstall SingleStore

On this page

Select a method to uninstall SingleStore

  • If you cluster was installed using MemSQL Ops and was later migrated to using SingleStore Tools, and/or is currently managed by SingleStore Tools: Uninstall using SingleStore Tools

Uninstall using SingleStore Toolbox

Depending on which version of SingleStore Toolbox you use to manage your cluster, you may remove the existing cluster either by a single command, or via sequence of commands.

Removing an existing cluster can be useful for deploying a new SingleStore cluster in its place, or after moving the existing cluster to another set of hosts.

Using either method, the SingleStore Tools-related binaries (Toolbox and client) can safely be deleted once the SingleStore cluster has been removed. If you plan to deploy a new SingleStore cluster, there is no need to delete these binaries.

SingleStore Toolbox 1.6.4 and later

As of SingleStore Toolbox 1.6.4, you may use a single command to remove a SingleStore cluster. The command will delete all data, delete all SingleStore nodes, and unregister all hosts.

Caution

Removing a SingleStore cluster with this command is irreversible.

Run the following command on the Master Aggregator and follow the prompts to remove the cluster.

sdb-deploy destroy-cluster

Refer to sdb-deploy destroy-cluster for more information.

SingleStore Toolbox 1.6.3 and earlier

If you’re using SingleStore Toolbox 1.6.3 or earlier to manage your SingleStore cluster, run the following commands in the following sequence to remove a SingleStore cluster.

  1. Stop all SingleStore nodes and delete them.

    sdb-admin delete-node --all --stop

  2. Uninstall all versions of SingleStore.

    sdb-deploy uninstall --all --all-versions

  3. Unregister all SingleStore hosts.

    sdb-toolbox-config unregister-host --all

  4. Confirm that SingleStore has been uninstalled.

    sdb-toolbox-config list-hosts

Last modified: December 16, 2022

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