Bug #32658 Typo in DUMP 8011 output

Submitted: 23 Nov 2007 13:55 Modified: 2 Jun 2009 10:49
Reporter: Jon Stephens Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.2 OS:Any
Assigned to: CPU Architecture:Any
Tags: CGE-6.2.9, cluster, dump, NDB_MGM

[23 Nov 2007 13:55] Jon Stephens
Description:
"Subscription" is misspellt in output of ALL DUMP 8011

How to repeat:
jon@flundra:~/svn> tail ~/bin/mysql-5.1-telco-6.2/libexec/ndb_3_cluster.log

2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 1: -- Starting dump of subscribers --
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 1: Table: 2 ver: 4294967040 #n: 1 (ref,data,subscritopn)
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 1:  [ 80010004 24 0 ]
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 1: Table: 3 ver: 4294967040 #n: 1 (ref,data,subscritopn)
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 1:  [ 80010004 28 1 ]
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 1: Table: 4 ver: 4294967040 #n: 1 (ref,data,subscritopn)
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 1:  [ 80020004 24 2 ]
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 1: -- Ending dump of subscribers --
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 2: -- Starting dump of subscribers --
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 2: Table: 2 ver: 4294967040 #n: 1 (ref,data,subscritopn)
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 2:  [ 80010004 24 0 ]
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 2: Table: 3 ver: 4294967040 #n: 1 (ref,data,subscritopn)
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 2:  [ 80010004 28 1 ]
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 2: Table: 4 ver: 4294967040 #n: 1 (ref,data,subscritopn)
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 2:  [ 80020004 24 2 ]
2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 2: -- Ending dump of subscribers --

Suggested fix:
Change "subscritopn" to "subscription".
[2 Jun 2009 9:53] Henrik Ingo
Turns out the output of ALL DUMP 8011 seems to have been rewritten at some point. This bug does not exist anymore in 7.0.7.
[2 Jun 2009 10:03] Henrik Ingo
ndb_mgm> show
Cluster Configuration
---------------------
[ndbd(NDB)]     2 node(s)
id=2    @127.0.0.1  (mysql-5.1.34 ndb-7.0.7, Nodegroup: 0, Master)
id=3    @127.0.0.1  (mysql-5.1.34 ndb-7.0.7, Nodegroup: 0)

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

[mysqld(API)]   1 node(s)
id=7    @127.0.0.1  (mysql-5.1.34 ndb-7.0.7)

ndb_mgm> all dump 8011
Sending dump signal with data:
0x00001f4b Sending dump signal with data:
0x00001f4b
ndb_mgm>                                       

$ tail -f mysql-cluster/ndb_1_cluster.log
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3: -- Starting dump of subscribers --
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3: Table 4 ver 1
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3:  Subcription 0
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3:   Subscriber [ 80020007 24 0 ]
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3: Table 4 #subscribers 1
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3: Table 5 ver 1
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3:  Subcription 1
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3:   Subscriber [ 80020007 28 1 ]
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3: Table 5 #subscribers 1
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3: Table 6 ver 1
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3:  Subcription 2
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3:   Subscriber [ 80030007 24 2 ]
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3: Table 6 #subscribers 1
2009-06-02 12:51:01 [MgmSrvr] INFO     -- Node 3: -- Ending dump of subscribers
[2 Jun 2009 10:49] Jon Stephens
The problem isn't found in a build from the 7.1 tree, either.

I don't see any reason to keep this open, so closing as Can't Repeat.
[2 Jun 2009 10:56] Jon Stephens
Doesn't appear in ndb-6.3.26, either.

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

Page generated in 0.040 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.