MySQL Forums
Forum List  »  NDB clusters

Re: Failed to allocate nodeid, error: 'Error: Could not alloc node id at .. : Connection done from wrong host
Posted by: Mikael Ronström
Date: July 12, 2017 03:11PM

2017-07-12T08:44:51.597473Z 0 [ERROR] Too many arguments (first extra is 'ndb-connectstring=10.215.2.74').
2017-07-12T08:44:51.597494Z 0 [Note] Use --verbose --help to get a list of available options!
2017-07-12T08:44:51.597497Z 0 [ERROR] Aborting

The above error implies that you have executed something like this:
mysqld ndb-connectstring=10.215.2.74

It should be
mysqld --ndb-connectstring=10.215.2.74

I also think that it is advisable to use
--ndb-nodeid=X when starting NDB data nodes (ndbd)
and even more important when starting the NDB
management server. I suggest that you also add
node id in the configuration to the NDB management
server as you have done to the NDB data nodes.

When starting the mysqld program you can use the following
if you also want to specify the node id used by MySQL Servers.

mysqld --ndbcluster --ndb-connectstring=10.215.2.74
--ndb-cluster-connection-pool-nodeids=4 &

After carefully reading your error logs and various posts I think
I also concluded that you get problems due to that the old configuration
is still lingering there.

When you want to start from scratch you should
ensure that you start the NDB management server with
--initial.

Here is a cut from the book on MySQL Cluster I am currently
writing on:

The ndb_mgmd program will ensure that all changes to the NDB configuration database is the same in all NDB management server.

In effect the ndb_mgmd maintains a very simple distributed database. It is created the first time one starts by using the --config-file option. This parameters points to the NDB configuration file.

If the directory already contains a binary configuration file then the configuration file will be ignored. If it is desirable to start a new cluster from scratch one can scrap the old configuration and overwrite it with a new configuration using the --initial flag. This flag should NEVER be used to update the configuration in a running cluster.

Hope this helps.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Failed to allocate nodeid, error: 'Error: Could not alloc node id at .. : Connection done from wrong host
29
July 12, 2017 03:11PM


Sorry, only registered users may post in this forum.

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.