Re: Node2 & Node3 Cluster requires this node to be started with --initial

[Richard InTx]

well, at least I know know how to get to the "ndb_mgm" daemon prompt now. Thought I can't get into "mysqlcluster_ndb2_1" or "mysqlcluster_ndb1_3" because the are restarting (duh). For mysqlcluster_ndb1_1 it is just happy to say it isn't connected to ID 5 & 6 and vomits the errors I know about from their logging files.

"docker exec -it mysqlcluster_ndb1_1 ndb_mgm"

But this is what I see from Node1 (Zoo1):


[root@zoo1 ~]# docker exec -it mysqlcluster_ndb1_1 ndb_mgm
-- NDB Cluster -- Management Client --
ndb_mgm> show
Connected to Management Server at: zoo1:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 3 node(s)
id=4 @10.46.133.180 (mysql-5.7.22 ndb-7.5.10, Nodegroup: 0, *)
id=5 (not connected, accepting connect from zoo2)
id=6 (not connected, accepting connect from zoo3)

[ndb_mgmd(MGM)] 3 node(s)
id=1 @10.46.133.180 (mysql-5.7.22 ndb-7.5.10)
id=2 @10.46.133.181 (mysql-5.7.22 ndb-7.5.10)
id=3 @10.46.133.182 (mysql-5.7.22 ndb-7.5.10)

[mysqld(API)] 3 node(s)
id=7 @10.46.133.180 (mysql-5.7.22 ndb-7.5.10)
id=8 @10.46.133.181 (mysql-5.7.22 ndb-7.5.10)
id=9 @10.46.133.182 (mysql-5.7.22 ndb-7.5.10)

ndb_mgm> Node 5: Forced node shutdown completed. Occured during startphase 3. Caused by error 2311: 'Conflict when selecting restart type(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'.
Node 5: Forced node shutdown completed. Occured during startphase 3. Caused by error 2311: 'Conflict when selecting restart type(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'.
Node 6: Forced node shutdown completed. Occured during startphase 3. Caused by error 2311: 'Conflict when selecting restart type(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'.