Sign inTry Free

6. Checking Node, Partition, and Overall Database Health

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.

On this page

The next step in troubleshooting your cluster is checking its overall health.

  1. Go to the Studio Hosts and/or Nodes page(s) to ensure nodes are online.

    • Run show-leaves to get the id of any offline node. sdb-admin show-leaves

    • Then, bring the node(s) online with start-node. sdb-admin start-node <node-id>

  2. Go to the Databases page, and examine the suspect database.

    • Click on the database, check the Partitions tab, and make sure everything is online and attached.

  3. If there are offline or detached partitions, investigate the health of the nodes housing those partitions in Studio.

    Health Status of the partitions in the Database page.

Next Steps

  • If all nodes, partitions, and databases are healthy: continue to Step 7.

Last modified: July 17, 2024

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