Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

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, while SingleStore 9.0 is recommended for production workloads.

Combining Unlimited and Local Storage Databases

It is possible to create unlimited and local storage databases in the same cluster. However, unlimited storage databases tend to aggressively reserve space for the blob cache and fill it up, which can contribute to “Out of Disk” (OOD) errors. If you want to reserve a certain amount of space for local databases on the same cluster, then you must cap the unlimited storage database blob cache size by setting the maximum_blob_cache_size_mb variable. Set it to a value that leaves enough space for your local databases and any other requirements.

The maximum_blob_cache_size_mb variable is configured by default on startup, using heuristics. Users are likely to run into issues with disks smaller than 40GB, hence SingleStore also traces a warning on startup in this case.

To accommodate local databases you should manually set the maximum_blob_cache_size_mb variable to the initial default value minus the value you need for the local databases. This must be set on every leaf node manually since the available disk size can vary on each node. You will need to set it in the memsql.cnf file to preserve the value across restarts.

Last modified:

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