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: | |
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 |
[1 Dec 2004 19:12]
Warren Konkel
[1 Dec 2004 19:14]
Warren Konkel
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)
[2 Dec 2004 7:43]
Tomas Ulin
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.
[13 Mar 2014 13:33]
Omer Barnir
This bug is not scheduled to be fixed at this time.