# Memory Errors

## 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](https://docs.singlestore.com/db/v9.1/reference/troubleshooting-reference/identifying-and-reducing-memory-usage.md).

## 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](https://docs.singlestore.com/db/v9.1/reference/troubleshooting-reference/identifying-and-reducing-memory-usage.md).

## 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](https://docs.singlestore.com/db/v9.1/introduction/faqs/general.md) for more information.

To understand how to handle capacity limit errors with these new licenses, see the [Capacity Limit Errors](https://docs.singlestore.com/db/v9.1/reference/troubleshooting-reference/capacity-limit-errors.md) 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](https://portal.singlestore.com) 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](https://docs.singlestore.com/db/v9.1/introduction/faqs/general.md) for more information.

To understand how to handle capacity limit errors with these new licenses, see the [Capacity Limit Errors](https://docs.singlestore.com/db/v9.1/reference/troubleshooting-reference/capacity-limit-errors.md) 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](https://portal.singlestore.com) 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](https://docs.singlestore.com/db/v9.1/reference/troubleshooting-reference/identifying-and-reducing-memory-usage.md).

## 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](https://docs.singlestore.com/db/v9.1/reference/configuration-reference/cluster-configuration/system-requirements-and-recommendations.md)

## ERROR: "Memory usage by SingleStore for vector indexes (.. Mb) has reached the value of ‘max\_vector\_index\_cache\_memory\_mb’ global variable (.. Mb)."

## Issue

This error indicates that there is not enough room in the vector index cache to insert another index into the cache. That is, there are not sufficient items in the cache that can be evicted to make room for the new index or the new index is larger than the cache size.

This error may also result from reducing the value of `max_vector_index_cache_memory_percent`. When the value of `max_vector_index_cache_memory_percent` is reduced, the following occurs.

* The resize succeeds if the new percentage is a legal value.
* The next time the cache is used, for example when a query is run that uses a vector index, the engine evicts per-segment indexes that are not in use to reduce the size of the cache until the cache is smaller than the new limit.
* If there are not enough evictable per-segment indexes, the engine reports the above out of memory (OOM) error. 

## Solutions

To address this error, potential solutions are:

* Use a more compact index such as IVFPQ\_FS which compresses vectors and has a smaller memory footprint.
* Increase the value of `max_vector_index_cache_memory_percent` to increase the size of the vector index cache.

***

Modified at: February 12, 2025

Source: [/db/v9.1/reference/troubleshooting-reference/memory-errors/](https://docs.singlestore.com/db/v9.1/reference/troubleshooting-reference/memory-errors/)

(An index of the documentation is available at /llms.txt)