MySQL Forums
Forum List  »  NDB clusters

Node2 & Node3 Cluster requires this node to be started with --initial
Posted by: Richard InTx
Date: November 05, 2022 07:55AM

Hi all newbie here (well less than a newbie, idiot).

I have a 3 node MySQL cluster that was installed via Docker (MySQL Docker Image 7.5.10-1.1.5), which this deployment was created by someone that isn't available to me anymore. The DB is used for Grafana and each of the Grafana's are operational and the 3 Nodes Grafana DBs are in sync.

The problem is on Node2 (Zoo2) and Node3 (Zoo3) the NDBD keeps restarting. I am pretty sure the logging is telling me what do to with the "Cluster requires this node to be started with --initial" log entry. Though I can figure out what that really means or how to start the docker cluster node with "--initial"... because I am to stupid to figure it out with all the reading I have found on the internet about Docker/MySQL.

I do a apologize for coming in here with "Hat in Hand" and not being able to understand this MySQL Cluster setup myself. I hope not to be flamed to hard and someone will have pity on me.


{"log":"2022-11-05 13:41:43 [ndbd] INFO -- NDB start phase 1 completed\n","stream":"stdout","time":"2022-11-05T13:41:43.252099351Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Start phase 2 completed\n","stream":"stdout","time":"2022-11-05T13:41:43.252102151Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Phase 2 did more initialisations, master accepted our start, we started REDO log initialisations\n","stream":"stdout","time":"2022-11-05T13:41:43.252104554Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Start NDB start phase 2\n","stream":"stdout","time":"2022-11-05T13:41:43.252108664Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Request permission to start our node from master Starting\n","stream":"stdout","time":"2022-11-05T13:41:43.275526623Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Cluster requires this node to be started with --initial as partial start has been performed and this filesystem is unusable\n","stream":"stdout","time":"2022-11-05T13:41:43.282072895Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- DBDIH (Line: 2267) 0x00000002\n","stream":"stdout","time":"2022-11-05T13:41:43.282083458Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Error handler shutting down system\n","stream":"stdout","time":"2022-11-05T13:41:43.282094445Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Error handler shutdown completed - exiting\n","stream":"stdout","time":"2022-11-05T13:41:43.320431813Z"}
{"log":"2022-11-05 13:41:43 [ndbd] ALERT -- 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'.\n","stream":"stdout","time":"2022-11-05T13:41:43.375021266Z"}

f13e0be154f557317a34c6267b0a0847247aa4073775e7f3d46a3720da4b2043 10.46.133.180:5000/mysql/mysql-cluster "/entrypoint.sh mysqld --ndb-nodeid=8" 2 months ago Up 2 hours (healthy) mysqlcluster_mysql2_1
d80a9e1a859d01e3812c40d7802edeba62842906eed91c858c74f95a6d55bca3 10.46.133.180:5000/mysql/mysql-cluster "/entrypoint.sh ndbd --ndb-nodeid=5 --nowait-nodes=5,6" 2 months ago Up 40 seconds (health: starting) mysqlcluster_ndb2_1
724caf3849d69a72c135065c424a06813cff8e565f3dbe7054a91febe7dc08a7 10.46.133.180:5000/mysql/mysql-cluster "/entrypoint.sh ndb_mgmd --ndb-nodeid=2" 2 months ago Up 2 hours (unhealthy) mysqlcluster_management2_1



Edited 2 time(s). Last edit at 11/05/2022 08:31AM by Richard InTx.

Options: ReplyQuote


Subject
Views
Written By
Posted
Node2 & Node3 Cluster requires this node to be started with --initial
565
November 05, 2022 07:55AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.