Sign inTry Free

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.

Update Exporter CPU and Memory Limits

The SingleStore exporter container collects health and performance data about a running cluster. Should an exporter container continue to crash, additional CPU and/or memory resources can be assigned to it.

  • For the CPU, a value of 1.0 means one CPU. This value may also be fractional, such as 0.25 (25%) of a CPU.

  • For memory, desired memory values must be specified in megabytes (MB).

SingleStore aggregator nodes and leaf nodes can be assigned CPU and memory values independently. These values may be adjusted in the spec section of the sdb-cluster.yaml.

  • In the aggregatorSpec section, revise the cpu and/or the memoryMB values under the exporterConfig section

  • In the leafSpec section, revise the cpu and/or the memoryMB values under the exporterConfig section

When completed, apply these changes to the cluster.

spec:
  ...
  aggregatorSpec:
    ...
    exporterConfig:
      cpu: 0.25   # 1.0 means one cpu
      memoryMB: 256
  leafSpec:
    ...
    exporterConfig:
      cpu: 0.25   # 1.0 means one cpu
      memoryMB: 256

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