Sign inTry Free

Memory Errors

On this page

ERROR 1712: Not enough memory available to complete the current request. The request was not processed.

For potential causes and solutions, see Identifying and Reducing Memory Usage.

ERROR: 1720 - Memory usage by SingleStore for tables (XXXXX MB) has reached the value of maximum_table_memory global variable (YYYYY MB). This query cannot be executed.

For potential causes and solutions, see Identifying and Reducing Memory Usage.

ERROR 2373: Code generation for new statements is disabled because the total number of license units of capacity used on all leaf nodes is XX, which is above the limit of 4 for the SingleStore free license.

Issue

This error is displayed when the limit imposed by the free license has been exceeded. This error is returned when generating plans for new queries after the memory settings have been increased beyond the free tier capacity.

  • For a v1 license (now deprecated), this limit is 4 license units (8 vCPU / 32GB)

  • For a v2 license, this limit is 4 license units (8 vCPUs / 64GB / 1TB)

Refer to General for more information.

To understand how to handle capacity limit errors with these new licenses, see the Capacity Limit Errors topic.

Solutions

There are three potential solutions depending on what your needs are:

  • If you need a cluster with more than four license units, you will need additional/paid licenses (Standard or Enterprise). Sign up for a free 30-day trial and create an Enterprise License trial key before deploying a larger cluster.

  • Redeploy the cluster on a smaller set of machines that will keep you under the four-unit limit.

  • Deploy your cluster manually using the Comprehensive Install Guide, and reduce the memory limits on all nodes with the instructions below.

NUMA CPUs and Multiple Nodes per Host

If you have NUMA-capable CPUs on your host machine, and wish to run more than one node per host machine, then your maximum_memory value would have to be reduced according to the count of nodes per host.

Memory allocation is calculated as follows:

  • One node, default settings: maximum_memory = 90% of physical memory

  • Two nodes, set maximum_memory = (90% of physical memory) / 2 per node

  • Four nodes, set maximum_memory = (90% of physical memory) / 4 per node

ERROR 2374: Leaf or aggregator node could not be added because you are using the SingleStore free license which has a limit of 4 license units and after adding the node you would be using XX license units.

Issue

This error is displayed when the limit imposed by the free license has been exceeded. This error is returned when generating plans for new queries after the memory settings have been increased beyond the free tier capacity.

  • For a v1 license (now deprecated), this limit is 4 license units (8 vCPU / 32GB)

  • For a v2 license, this limit is 4 license units (8 vCPUs / 64GB / 1TB)

Refer to General for more information.

To understand how to handle capacity limit errors with these new licenses, see the Capacity Limit Errors topic.

Solutions

There are three potential solutions depending on what your needs are:

  • If you need a cluster with more than four license units, you will need additional/paid licenses (Standard or Enterprise). Sign up for a free 30-day trial and create an Enterprise License trial key before deploying a larger cluster.

  • Redeploy the cluster on a smaller set of machines that will keep you under the four-unit limit.

  • Deploy your cluster manually using the Comprehensive Install Guide, and reduce the memory limits on all nodes with the instructions below.

NUMA CPUs and Multiple Nodes per Host

If you have NUMA-capable CPUs on your host machine, and wish to run more than one node per host machine, then your maximum_memory value would have to be reduced according to the count of nodes per host.

Memory allocation is calculated as follows:

  • One node, default settings: maximum_memory = 90% of physical memory

  • Two nodes, set maximum_memory = (90% of physical memory) / 2 per node

  • Four nodes, set maximum_memory = (90% of physical memory) / 4 per node

ERROR: "Nonfatal buffer manager memory allocation failure. The maximum_memory parameter (XXXXX MB) has been reached.

For potential causes and solutions, see Identifying and Reducing Memory Usage.

Failed to allocate XXXXX bytes of memory from the operating system (Error 12: Cannot allocate memory). This is usually due to a misconfigured operating system or virtualization technology.

This error message indicates a host level misconfiguration in how the kernel is allowed to allocate memory. This causes the kernel to refuse memory allocation requests from the database, even when the database has not exceeded its limit. This can be caused by misconfiguration of any of the following:

  • low vm.max_map_count

  • high vm.min_free_kbytes

  • low vm.swappiness

  • vm.overcommit_memory

  • low vm.overcommit_ratio

  • inadequate Swap space

For more information about the recommended configuration of these settings, see System Requirements and Recommendations

Last modified: February 12, 2025

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

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