Bug #27444 DataMemory missing from report in cluster logs
Submitted: 26 Mar 2007 16:20 Modified: 2 Apr 2007 13:26
Reporter: Geert Vanderkelen
Status: Closed
Category:Server: Cluster Severity:S3 (Non-critical)
Version:mysql-5.1.15_ndb-6.1.5 OS:Linux (Linux)
Assigned to: Tomas Ulin Target Version:
Tags: ndb, reporting

[26 Mar 2007 16:20] Geert Vanderkelen 
Description:
When using the option MemReportFrequency the DataMemory is not showing for one data node
(usually the first one).

Doing a ALL DUMP 1000 in the ndb_mgm CLI every works as expected:

2007-03-26 16:10:23 [MgmSrvr] INFO     -- Node 3: Node 1: API mysql-5.1.15 ndb-6.1.5
2007-03-26 16:10:23 [MgmSrvr] INFO     -- Node 4: Node 1: API mysql-5.1.15 ndb-6.1.5
2007-03-26 16:10:23 [MgmSrvr] INFO     -- Node 4: Prepare arbitrator node 1
[ticket=4bac00018e955212]
2007-03-26 16:10:23 [MgmSrvr] INFO     -- Node 3: Started arbitrator node 1
[ticket=4bac00018e955212]

# Automated report of Memory report
2007-03-26 16:11:22 [MgmSrvr] INFO     -- Node 3: Index usage is 0%(8 8K pages of total
50464)
2007-03-26 16:11:22 [MgmSrvr] INFO     -- Node 4: Data usage is 0%(8 32K pages of total
15104)
2007-03-26 16:11:22 [MgmSrvr] INFO     -- Node 4: Index usage is 0%(8 8K pages of total
50464)

# ALL DUMP 1000 Output
2007-03-26 16:11:40 [MgmSrvr] INFO     -- Node 3: Data usage is 0%(8 32K pages of total
15104)
2007-03-26 16:11:40 [MgmSrvr] INFO     -- Node 3: Index usage is 0%(8 8K pages of total
50464)
2007-03-26 16:11:40 [MgmSrvr] INFO     -- Node 3: Resource 0 min: 0 max: 639 curr: 0
2007-03-26 16:11:40 [MgmSrvr] INFO     -- Node 4: Data usage is 0%(8 32K pages of total
15104)
2007-03-26 16:11:40 [MgmSrvr] INFO     -- Node 4: Index usage is 0%(8 8K pages of total
50464)
2007-03-26 16:11:40 [MgmSrvr] INFO     -- Node 4: Resource 0 min: 0 max: 639 curr: 0

# Automated report of Memory report
2007-03-26 16:12:22 [MgmSrvr] INFO     -- Node 3: Index usage is 0%(8 8K pages of total
50464)
2007-03-26 16:12:22 [MgmSrvr] INFO     -- Node 4: Data usage is 0%(8 32K pages of total
15104)
2007-03-26 16:12:22 [MgmSrvr] INFO     -- Node 4: Index usage is 0%(8 8K pages of total
50464)

How to repeat:
Setup simple cluster with 1 ndb_mgm and 2 ndbd's. Start them all with --initial using the
configuration attached to this report.

(During tests I found a case where doing a restart of the node not reporting the
DataMemory resulted in no reports at all anymore. Only the remaining node was getting log
entries in the cluster log, though node 3 was happily up and showing in the SHOW output.
I could not yet repeat that.)
[26 Mar 2007 16:24] Geert Vanderkelen 
Configuration file

Attachment: bug27444_config.ini (text/plain), 1.11 KiB.
[26 Mar 2007 16:25] Geert Vanderkelen 
Verified using MySQL 5.1.15-6.1.5 (telco).
[27 Mar 2007 10:59] 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/22986

ChangeSet@1.2448, 2007-03-27 11:12:26+02:00, tomas@whalegate.ndb.mysql.com +1 -0
  Bug #27444  	DataMemory missing from report in cluster logs
  - error in initial signal length giving uninitialized variable
[30 Mar 2007 11:28] Tomas Ulin 
5.1.18
[2 Apr 2007 13:26] Jon Stephens 
Thank you for your bug report. This issue has been committed to our source repository of
that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version,
including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented bugfix in 5.1.18 changelog.