Sign inTry Free

Important

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

Best Practices for Successful Rebalance Operations

  • Upgrade Sequence: Perform the engine upgrade to at least version 9.0 before initiating scale-out activities; versions 8.9 and 9.0 contain critical fixes that ensure a smoother scaling process.

  • Redundancy Level: Increase the cluster configuration to Redundancy 2. The setting of Redundancy 1 is not suitable for large production environments and poses significant risk during upgrades or failovers.

  • Storage Architecture: Utilize the standard configuration with local disks or high-quality direct-attached SAN LUNs/JBODs. SingleStore recommends against using "bottomless" storage or remote Linux file systems for on-premise deployments.

  • Memory Configuration:

    • Set maximum_memory to 90% of the host's physical RAM.

    • Set maximum_table_memory to 90% of the configured maximum_memory.

  • Resource Management: Configure Resource Pools with strict memory and CPU restrictions to isolate workloads and protect cluster stability.

  • Partition Sizing: Adhere to best practices regarding the number of partitions per core. Utilizing smaller, more numerous partitions reduces rebalance times and lowers the risk of failure during partition moves.

  • Operational Maintenance: Use the REBALANCE PARTITIONS ... WITH KILL command during maintenance; this ensures slow mergers are terminated automatically to prevent blocking.

  • Professional Services: SingleStore recommends engaging Support for major activities (such as upgrades or expansions) to ensure continuous, dedicated on-call support.

Last modified: March 13, 2026

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

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