Bug #39834 all report memory does not report to stdout

• Submitted: 3 Oct 2008 10:33
• Modified: 12 Dec 2008 13:08
• Reporter: Oli Sennhauser
• Status: Duplicate
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• Version: mysql-5.1.27 ndb-6.3.17
• OS: Any
• CPU Architecture: Any

[3 Oct 2008 10:33] Oli Sennhauser

Description:
all report mem on the ndb_mgm does sometimes NOT report to stdout but to cluster log.

How to repeat:
ndb_mgm> show
Cluster Configuration
---------------------
[ndbd(NDB)]     2 node(s)
id=10   @127.0.0.1  (mysql-5.1.27 ndb-6.3.17, Nodegroup: 0, Master)
id=11   @127.0.0.1  (mysql-5.1.27 ndb-6.3.17, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @127.0.0.1  (mysql-5.1.27 ndb-6.3.17)

[mysqld(API)]   7 node(s)
id=20   @127.0.0.1  (mysql-5.1.27 ndb-6.3.17)
id=21   @127.0.0.1  (mysql-5.1.27 ndb-6.3.17)
id=22   @127.0.0.1  (mysql-5.1.27 ndb-6.3.17)
id=23 (not connected, accepting connect from any host)
id=24 (not connected, accepting connect from any host)
id=25 (not connected, accepting connect from any host)
id=26 (not connected, accepting connect from any host)

ndb_mgm> all report mem

Suggested fix:
output should report mem statistics. This might be related to bug #31542 and #37632.

[3 Oct 2008 10:34] Oli Sennhauser

config.ini

Attachment: config.ini (application/octet-stream, text), 1.90 KiB.

[3 Oct 2008 11:54] Oli Sennhauser

Uppps. Found out, that I was connecting with an ndb_mgm 6.0.4 client against the 6.3.17 ndb_mgmd... But it still should display correctly, should it not? With the 6.3.17 ndb_mgm client it works fine.

[3 Oct 2008 20:38] Sveta Smirnova

Thank you for the report.

>  Found out, that I was connecting with an ndb_mgm 6.0.4 client against the 6.3.17
ndb_mgmd... But it still should display correctly, should it not?

As we don't backport bug fixes is it OK to close this report as "Can't repeat"?

[12 Dec 2008 13:11] Jon Stephens

Duplicate of Bug#31542