MySQL Bugs: #11750: All IP information is lost after ndb

Bug #11750	All IP information is lost after ndb_mgmd restart
Submitted:	5 Jul 2005 21:05	Modified:	13 Jul 2005 11:37
Reporter:	Jonathan Miller	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	4.1	OS:	Linux (Linux)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
killing and restarting ndb_mgmd causes all associated node, and api IP addresses to be lost.
ndb_mgm> show
Cluster Configuration
---------------------
[ndbd(NDB)]     4 node(s)
id=2    @##.###.1.93  (Version: 5.1.0, Nodegroup: 0, Master)
id=3    @##.###.1.94  (Version: 5.1.0, Nodegroup: 0)
id=4    @##.###.1.93  (Version: 5.1.0, Nodegroup: 1)
id=5    @##.###.1.94  (Version: 5.1.0, Nodegroup: 1)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @##.###.1.93  (Version: 5.1.0)

[mysqld(API)]   9 node(s)
id=6    @##.###.1.93  (Version: 5.1.0)
id=7 (not connected, accepting connect from ndb08)
id=8 (not connected, accepting connect from ndb08)
id=9 (not connected, accepting connect from ndb09)
id=10 (not connected, accepting connect from ndb09)
id=11 (not connected, accepting connect from ndb09)
id=14 (not connected, accepting connect from ndb08)
id=15 (not connected, accepting connect from ndb09)
id=16 (not connected, accepting connect from ndb10)

ndb_mgm> exit
ndb08:/space/run> killall ndb_mgmd
ndb08:/space/run> ndb_mgmd -f config.ini
ndb08:/space/run> ndb_mgm $ndbc
-- NDB Cluster -- Management Client --
ndb_mgm> show
Connected to Management Server at: ndb08:14000
Cluster Configuration
---------------------
[ndbd(NDB)]     4 node(s)
id=2   (Version: 5.1.0, Nodegroup: 0, Master)
id=3   (Version: 5.1.0, Nodegroup: 0)
id=4   (Version: 5.1.0, Nodegroup: 1)
id=5   (Version: 5.1.0, Nodegroup: 1)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @10.100.1.93  (Version: 5.1.0)

[mysqld(API)]   9 node(s)
id=6   (Version: 5.1.0)
id=7 (not connected, accepting connect from ndb08)
id=8 (not connected, accepting connect from ndb08)
id=9 (not connected, accepting connect from ndb09)
id=10 (not connected, accepting connect from ndb09)
id=11 (not connected, accepting connect from ndb09)
id=14 (not connected, accepting connect from ndb08)
id=15 (not connected, accepting connect from ndb09)
id=16 (not connected, accepting connect from ndb10)

ndb_mgm>

I don't have a 5.0 clone to test this with, but would assume since it is in 5.1 it would be there as well.

How to repeat:
see above.

Suggested fix:
If the ndb_mgmd is smart enough to know which data nodes are running when it restarts, it should be able to list their IP addresses as well.

Verified w/latest bk tree of 5.0

duplicate of #11596