Re: Failed to allocate nodeid for mysqld
Hi Deepak
You have ndb_cluster_connection_pool=16, this means that the mysql server will connect to cluster using 16 connections, and by that also need 16 node ids.
You need lots of more [API] sections in config.ini, at least 16 per mysqld, and a few more to be able to run arbitrarily ndb command line tool.
But first thing to try would be to revert that settings and keep the default (1) for ndb_cluster_connection_pool. Only raise it in small steps if there are reason to believe it is needed and make sure to follow up with measurements.
In later releases (8.0) the default setting is good, in a few cases using 2 has given some improvement but this is not the first parameter to change.
Also if you set ndb_cluster_connection_pool to more than 1 it is recommended to also set the node id to use for each connection with ndb-cluster-connection-pool-nodeids, else there may be issues when a mysql server want to reconnect to a cluster while other programs, other mysqld or ndb command line tools, starting or reconnecting without explicit node id to use since they then may compete to reuse same node ids.
Regards,
Mauritz
Subject
Views
Written By
Posted
2137
June 21, 2021 12:44PM
832
June 21, 2021 01:17PM
762
June 21, 2021 01:59PM
793
June 22, 2021 05:24AM
788
June 22, 2021 06:47AM
817
June 22, 2021 06:49AM
762
June 22, 2021 08:16AM
788
June 23, 2021 04:48AM
736
June 23, 2021 05:58AM
646
July 03, 2021 09:12AM
Re: Failed to allocate nodeid for mysqld
690
July 03, 2021 11:20AM
604
July 06, 2021 04:27AM
651
July 06, 2021 06:34AM
736
July 06, 2021 10:04AM
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.