Bug #51735 NDBINFO memoryusage table shows different results from ALL REPORT MEMORYUSAGE;

Submitted: 4 Mar 2010 19:13 Modified: 16 Mar 2010 10:27
Reporter: Matthew Montgomery Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:7.1.2-beta OS:Any
Assigned to: Magnus Blåudd CPU Architecture:Any

[4 Mar 2010 19:13] Matthew Montgomery
Description:
ALL REPORT MEMORYUSAGE and mysql> ndbinfo.memoryusage do not report the same results for DataMemory.  IndexMemory usage is reported correctly.

How to repeat:
mysql> select * from memoryusage; 
+---------+--------------+------+------+
| node_id | memory_type  | used | max  |
+---------+--------------+------+------+
|       2 | DATA_MEMORY  |  295 |  424 |
|       3 | DATA_MEMORY  |  295 |  424 |
|       2 | INDEX_MEMORY |   56 |  672 |
|       3 | INDEX_MEMORY |   56 |  672 |
+---------+--------------+------+------+
4 rows in set (0.28 sec)

mysql> select * from ndb$resources where resource_id =3; 
+---------+-------------+----------+------+------+------+
| node_id | resource_id | reserved | used | max  | high |
+---------+-------------+----------+------+------+------+
|       2 |           3 |      424 |  295 |  424 |    0 |
|       3 |           3 |      424 |  295 |  424 |    0 |
+---------+-------------+----------+------+------+------+
2 rows in set (0.04 sec)

mysql>\q
Bye
matt@silo:~/mysql/sandbox/7.1.1$ ndb_mgm
-- NDB Cluster -- Management Client --
ndb_mgm> all report mem; 
Connected to Management Server at: localhost:1186

ndb_mgm> Node 2: Data usage is 49%(127 32K pages of total 256)
Node 2: Index usage is 8%(56 8K pages of total 672)
Node 3: Data usage is 49%(127 32K pages of total 256)
Node 3: Index usage is 8%(56 8K pages of total 672)

Suggested fix:
Fix output of ndb$resources

mysql> select * from ndb$resources where resource_id =3; 
+---------+-------------+----------+------+------+------+
| node_id | resource_id | reserved | used | max  | high |
+---------+-------------+----------+------+------+------+
|       2 |           3 |      424 |  295 |  424 |    0 |
|       3 |           3 |      424 |  295 |  424 |    0 |
+---------+-------------+----------+------+------+------+
2 rows in set (0.04 sec)
[5 Mar 2010 15:03] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/102446
[16 Mar 2010 8:22] Magnus Blåudd
Pushed to 7.0.14 and 7.1.3-beta
[16 Mar 2010 8:22] Bugs System
Pushed into 5.1.44-ndb-7.0.14 (revid:magnus.blaudd@sun.com-20100316080614-xsy933pm0m57fyc6) (version source revid:magnus.blaudd@sun.com-20100316080614-xsy933pm0m57fyc6) (merge vers: 5.1.44-ndb-7.0.14) (pib:16)
[16 Mar 2010 10:27] Jon Stephens
Documented bugfix in the NDB-7.1.3 changelog as follows:

        Values shown for the DATA_MEMORY column of the
        ndbinfo.memoryusage table did not match those shown by the
        ndb_mgm client REPORT MEMORYUSAGE command.

Closed.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.054 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.