Sign inTry Free

Disk Spilling Errors

On this page

ERROR 2630 (HY000): Available disk space is below the value of 'spilling_minimal_disk_space' global variable. Spilling is aborted.

Issue

This error indicates that a query needs to spill but the disk available size is below the value of the spilling_minimal_disk_space variable.

ERROR 2630 (HY000): Spilling disk usage (x MB) exceeds the limit (y MB) set through the global variable 'spilling_maximum_size_percent'(z). Spilling is aborted. New request size: n bytes

Issue

This error occurs when a query's disk spilling size requirement exceeds the maximum disk usage limit.

For example:

ERROR 2630 (HY000): Spilling disk usage (25990.000000 MB) exceeds the limit (25982.400000 MB) set through global variable 'spilling_maximum_size_percent'(-1.000000). Spilling is aborted. New request size: 96 bytes.

ERROR 2630 (HY000): Spilling may interfere with replication which is low on disk space to store data in the blob cache. Spilling is aborted. The current max blob cache size after adjusted for low disk and spilling: x MB, current spilling size: y MB"

Issue

This error occurs when the columnstore blob cache is low during database replication, query spilling may be temporarily blocked.  Queries that need to spill may hit this error.

ERROR: Spilling disk usage (%f MB) exceeds the limit (%f MB) set through global variable 'spilling_maximum_disk_percent'(%f). Spilling is aborted. New request size: %lu bytes

Issue

This error occurs when a query run needs to spill but the variable spilling_maximum_size_percent is equal to zero.

Last modified: May 4, 2023

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