Movatterモバイル変換

Querying this table provides information similar to that provided by theALL REPORT MemoryUsage command in thendb_mgm client, or logged byALL DUMP 1000.

Thememoryusage table contains the following columns:

Notes

Thetotal column represents the total amount of memory in bytes available for the given resource (data memory or index memory) on a particular data node. This number should be approximately equal to the setting of the corresponding configuration parameter in theconfig.ini file.

Suppose that the cluster has 2 data nodes having node IDs5 and6, and theconfig.ini file contains the following:

[ndbd default]DataMemory = 1GIndexMemory = 1G

Suppose also that the value of theLongMessageBuffer configuration parameter is allowed to assume its default (64 MB).

The following query shows approximately the same values:

mysql> SELECT node_id, memory_type, total     > FROM ndbinfo.memoryusage;+---------+---------------------+------------+| node_id | memory_type         | total      |+---------+---------------------+------------+|       5 | Data memory         | 1073741824 ||       5 | Index memory        | 1074003968 ||       5 | Long message buffer |   67108864 ||       6 | Data memory         | 1073741824 ||       6 | Index memory        | 1074003968 ||       6 | Long message buffer |   67108864 |+---------+---------------------+------------+6 rows in set (0.00 sec)

In this case, thetotal column values for index memory are slightly higher than the value set ofIndexMemory due to internal rounding.

For theused_pages andtotal_pages columns, resources are measured in pages, which are 32K in size forDataMemory and 8K forIndexMemory. For long message buffer memory, the page size is 256 bytes.