MySQL Bugs: #6923: ndb_mgm doesn't show connected IP's after ndb

Bug #6923	ndb_mgm doesn't show connected IP's after ndb_mgmd restart
Submitted:	1 Dec 2004 19:12	Modified:	2 Dec 2004 7:43
Reporter:	Warren Konkel	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	4.1.7	OS:	FreeBSD (FreeBSD)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
The ndb_mgm appliation won't show IP addresses of nodes which automatically reconnected after a ndb_mgmd shutdown/crash.  

This is before the shutdown and is what it should look like (note the @128.121.212.238 part of id 2, 3 and 5):

NDB> show
Cluster Configuration
---------------------
[ndbd(NDB)]     2 node(s)
id=2    @128.121.212.238  (Version: 3.5.3, Nodegroup: 0)
id=4 (not connected, accepting connect from db5.mindtown.net)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @128.121.212.238  (Version: 3.5.3)

[mysqld(API)]   2 node(s)
id=3    @128.121.212.238  (Version: 3.5.3)
id=5    @128.121.212.237  (Version: 3.5.3)

Then if you exit ndb_mgm, kill -9 the process, restart ndb_mgmd, and run the "SHOW" command again, you get:

NDB> show
Cluster Configuration
---------------------
[ndbd(NDB)]     2 node(s)
id=2   (Version: 3.5.3, Nodegroup: 0)
id=4 (not connected, accepting connect from db5.mindtown.net)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @128.121.212.238  (Version: 3.5.3)

[mysqld(API)]   2 node(s)
id=3   (Version: 3.5.3)
id=5   (Version: 3.5.3)

Notice nodes 2, 3 and 5 are still connected (running version 3.5.3), but the IP they're coming from is no longer displayed.

How to repeat:
1. start ndb_mgmd
2. connect multiple nodes
3. stop ndb_mgmd
4. start ndb_mgmd
5. run ndb_mgm and type "SHOW"
6. observe

Suggested fix:
not sure.

If you disconnect a node (either ndbd or mysqld) and reconnect it, the IP then shows up (note nodeid=5 has an @IP now... it was restarted):

NDB> show
Cluster Configuration
---------------------
[ndbd(NDB)]     2 node(s)
id=2   (Version: 3.5.3, Nodegroup: 0)
id=4 (not connected, accepting connect from db5.mindtown.net)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @128.121.212.238  (Version: 3.5.3)

[mysqld(API)]   2 node(s)
id=3   (Version: 3.5.3)
id=5    @128.121.212.237  (Version: 3.5.3)

Yes,

this is known.

We will eventually fix it.  Now it serves a rather important purpose.  When you restart the management server it will have read a new configuration which may differ from the old one.

The fact that the ip-adress is not shown for a particular node, shows that this node has not fetched this "new" configuration.

Fetching a new configuration like that is however not something we support.  Once we've added that, the ip-address will show up.

This bug is not scheduled to be fixed at this time.