My Oracle Support Banner

Table is Full Error for NDBCluster Due to IndexMemory Despite Free Memory After Increasing the Number of LDM/LQH Threads; Got Error 625 'Out of Memory in Ndb Kernel, Hash Index Part (Increase IndexMemory)' from NDB (Doc ID 1942737.1)

Last updated on MARCH 08, 2017

Applies to:

MySQL Cluster - Version 6.3 and later
Information in this document applies to any platform.

Symptoms

When executing a statement that causes the amount of IndexMemory to change following error occurs:

mysql> INSERT INTO t1 SELECT NULL FROM t1 LIMIT 2048;
ERROR 1114 (HY000): The table 't1' is full
mysql> SHOW WARNINGS;
+---------+------+----------------------------------------------------------------------------------------------+
| Level   | Code | Message                                                                                      |
+---------+------+----------------------------------------------------------------------------------------------+
| Warning | 1296 | Got error 625 'Out of memory in Ndb Kernel, hash index part (increase IndexMemory)' from NDB |
| Error   | 1114 | The table 't1' is full                                                                       |
+---------+------+----------------------------------------------------------------------------------------------+
2 rows in set (0.06 sec)

 

However the memory usage does not suggest that the data nodes are out of IndexMemory:

mysql> SELECT *, ROUND(100*used_pages/total_pages, 2) AS 'Used%' FROM ndbinfo.memoryusage;
+---------+---------------------+----------+------------+----------+-------------+-------+
| node_id | memory_type         | used     | used_pages | total    | total_pages | Used% |
+---------+---------------------+----------+------------+----------+-------------+-------+
|       1 | Data memory         | 18907136 |        577 | 26214400 |         800 | 72.13 |
|       1 | Index memory        |  5595136 |        683 | 11534336 |        1408 | 48.51 |
|       1 | Long message buffer |   393216 |       1536 | 67108864 |      262144 |  0.59 |
|       2 | Data memory         | 18907136 |        577 | 26214400 |         800 | 72.13 |
|       2 | Index memory        |  5595136 |        683 | 11534336 |        1408 | 48.51 |
|       2 | Long message buffer |   524288 |       2048 | 67108864 |      262144 |  0.78 |
+---------+---------------------+----------+------------+----------+-------------+-------+
6 rows in set (0.02 sec)

 

Changes

The number of LDM (also known as LQH) threads was increased. This can happen either due to changing MaxNoOfExecutionThreads or ThreadConfig.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.