| Bug #55203 | NDB node keep starting state for long time after changes on config.ini | ||
|---|---|---|---|
| Submitted: | 13 Jul 2010 6:46 | Modified: | 16 Sep 2010 11:13 |
| Reporter: | Jabba Jabba | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S1 (Critical) |
| Version: | mysql-5.1-telco-7.1 | OS: | Linux (Red Hat Enterprise Linux Server release 5.4) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | 7.1.4b | ||
[13 Jul 2010 6:46]
Jabba Jabba
[13 Jul 2010 8:43]
Jabba Jabba
We have performed further testing, no matter we have change any parameter in the config.ini and then execute ndb_mgmd -f /var/lib/mysql-cluster/config.ini --reload The problem does occur. If we remove the ndb_1_config.bin.2 and use the ndb_1_config.bin.1 for starting the ndbd. It back to normal state. Actually what is the root cause for the ndbd node keep waiting for the other node? 2010-07-13 16:42:21 [MgmtSrvr] INFO -- Node 2: Initial start, waiting for 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2010-07-13 16:42:24 [MgmtSrvr] INFO -- Node 2: Initial start, waiting for 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2010-07-13 16:42:27 [MgmtSrvr] INFO -- Node 2: Initial start, waiting for 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2010-07-13 16:42:30 [MgmtSrvr] INFO -- Node 2: Initial start, waiting for 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2010-07-13 16:42:33 [MgmtSrvr] INFO -- Node 2: Initial start, waiting for 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] For normal startup, it will shows: 2010-07-11 16:00:52 [MgmtSrvr] INFO -- Node 2: Waiting 30 sec for nodes 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2010-07-11 16:00:55 [MgmtSrvr] INFO -- Node 2: Waiting 27 sec for nodes 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2010-07-11 16:00:58 [MgmtSrvr] INFO -- Node 2: Waiting 24 sec for nodes 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2010-07-11 16:01:01 [MgmtSrvr] INFO -- Node 2: Waiting 21 sec for nodes 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2010-07-11 16:01:04 [MgmtSrvr] INFO -- Node 2: Waiting 18 sec for nodes 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2010-07-11 16:01:07 [MgmtSrvr] INFO -- Node 2: Waiting 15 sec for nodes 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2010-07-11 16:01:10 [MgmtSrvr] INFO -- Node 2: Waiting 12 sec for nodes 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2010-07-11 16:01:13 [MgmtSrvr] INFO -- Node 2: Waiting 9 sec for nodes 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ]
[16 Aug 2010 11:13]
Hartmut Holzgraefe
How exactly do you start the data node(s)? The log snippets you provided indicate that you are using "ndbd --initial", and with --initial neither StartPartialTimeout nor StartPartitionedTimeout take any effect, they are treated as if they were set to zero and nodes will not start after timeout but will wait for all other nodes to show up indefinitely.
[16 Sep 2010 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[9 May 2017 12:20]
Ralph Anthony Planteras
I have the same experience. Does anyone knows how to fix this? Thanks. Version: mysql-5.7.18 ndb-7.5.6 OS: CentOS Linux release 7.3.1611 MGM Node: [ndb_mgm display] ndb_mgm> show Cluster Configuration --------------------- [ndbd(NDB)] 2 node(s) id=2 @192.168.50.53 (mysql-5.7.18 ndb-7.5.6, starting, Nodegroup: 0) id=3 @192.168.50.55 (mysql-5.7.18 ndb-7.5.6, Nodegroup: 0) [ndb_mgmd(MGM)] 1 node(s) id=1 @192.168.50.51 (mysql-5.7.18 ndb-7.5.6) [mysqld(API)] 2 node(s) id=4 @192.168.50.52 (mysql-5.7.18 ndb-7.5.6) id=5 @192.168.50.54 (mysql-5.7.18 ndb-7.5.6) [logfile: /var/lib/mysql-cluster/ndb_1_cluster.log] 2017-05-09 20:07:50 [MgmtSrvr] ALERT -- Node 2: Forced node shutdown completed. Occured during startphase 0. Initiated by signal 9. 2017-05-09 20:07:50 [MgmtSrvr] ALERT -- Node 1: Node 2 Disconnected 2017-05-09 20:07:52 [MgmtSrvr] INFO -- Node 3: NR Status: node=2,OLD=Allocated node id,NEW=Allocated node id 2017-05-09 20:07:52 [MgmtSrvr] INFO -- Alloc node id 2 succeeded 2017-05-09 20:07:52 [MgmtSrvr] INFO -- Nodeid 2 allocated for NDB at 192.168.50.53 2017-05-09 20:07:52 [MgmtSrvr] INFO -- Node 1: Node 2 Connected 2017-05-09 20:07:56 [MgmtSrvr] INFO -- Node 2: Initial start, waiting for 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2017-05-09 20:07:59 [MgmtSrvr] INFO -- Node 2: Initial start, waiting for 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2017-05-09 20:08:02 [MgmtSrvr] INFO -- Node 2: Initial start, waiting for 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2017-05-09 20:08:05 [MgmtSrvr] INFO -- Node 2: Initial start, waiting for 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2017-05-09 20:08:08 [MgmtSrvr] INFO -- Node 2: Initial start, waiting for 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] 2017-05-09 20:08:11 [MgmtSrvr] INFO -- Node 2: Initial start, waiting for 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ]
