Important

Self-managed SingleStore will soon transition from version 9.1 RC to version 10. This new semantic versioning scheme will provide SingleStore with finer control over engine and feature releases that were not possible with the current versioning scheme.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10 prior to its general availability. Ahead of this transition, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 10.

Cluster Management with Tools

Tools Overview

SingleStore provides a suite of tools to manage and interact with your cluster.

SingleStore Toolbox

For clusters running MemSQL 6.7 or later, you should use SingleStore Toolbox to deploy, administer, and manage your cluster. The associated command-line tools are packaged in Debian, RPM, and tarball files which allows them to be part of common automated deployment workflows.

Most of the tools are part of the singlestoredb-toolbox package; however, the lower-level management tool, memsqlctl, is part of the singlestoredb-server package (along with the SingleStore engine itself).

For more information on the tools, see the following links:

  • sdb-deploy. Installs memsqlctl and the SingleStore database engine to hosts in the cluster.

  • sdb-admin. Helps you manage a SingleStorecluster.

  • sdb-report. Collects and performs diagnostic checks on your cluster.

  • sdb-toolbox-config. Performs host registration.

  • memsqlctl. Provides lower-level access to manage nodes on a host.

SQL Clients and Tools

The following tools allow you to issue queries against your cluster, and as with the management tools above, they are packaged in Debian, RPM, or tar files for easy deployment and management:

In this section

Last modified:

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.