Bug #26956 Wrong Version reported for ndb_mgmd with ndb_mgm

• Submitted: 8 Mar 2007 10:35
• Modified: 29 Mar 2007 3:26
• Reporter: Jens Kruse
• Status: Can't repeat
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• Version: 5.1.16
• OS: xubuntu 6.06
• Assigned to: li zhou
• CPU Architecture: Any
• Tags: cluster, STATUS, version

[8 Mar 2007 10:35] Jens Kruse

Description:
ndb_mgm reports the wrong version (0.0.0) asking for the status of node 1

How to repeat:
ndb_mgm> SHOW
Cluster Configuration
---------------------
[ndbd(NDB)]     2 node(s)
id=2    @127.0.0.1  (Version: 5.1.16, Nodegroup: 0, Master)
id=3    @127.0.0.1  (Version: 5.1.16, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @127.0.0.1  (Version: 5.1.16)

[mysqld(API)]   1 node(s)
id=4 (not connected, accepting connect from any host)

ndb_mgm> STATUS
Invalid command: STATUS
Type HELP for help.

ndb_mgm> 1 STATUS
Node 1: connected (Version 0.0.0)

ndb_mgm> 2 STATUS
Node 2: started (Version 5.1.16)

ndb_mgm> 3 STATUS
Node 3: started (Version 5.1.16)

ndb_mgm> ALL STATUS
Node 2: started (Version 5.1.16)
Node 3: started (Version 5.1.16)

[8 Mar 2007 16:38] Hartmut Holzgraefe

5.0 reports "not connected", 5.1 "connected (Version 0.0.0)" for non-data nodes (both ndb_mgmd and mysqld) which is confusing

If the version can't be retrieved it should be excluded from the output