NDB Cluster Manager Failure To Allocate NodeId

(Doc ID 2084854.1)

Last updated on JULY 24, 2017

Applies to:

MySQL Cluster - Version 7.3 and later
Information in this document applies to any platform.

Symptoms

Typically in a new MySQL Cluster Environment, or potentially after a configuration change , the management node will issue an error on a cluster start ( rolling or otherwise ) similar to;

2015-11-18 21:00:55 [MgmtSrvr] WARNING -- Failed to allocate nodeid for API at 172.16.22.91. Returned error: 'Id 111 already allocated by another node.'

 

This error is misleading.

2015-11-18 21:00:55 [MgmtSrvr] WARNING -- Failed to allocate nodeid for API at 172.16.22.91. Returned error: 'Id 111 already allocated by another node.'
2015-11-18 21:00:58 [MgmtSrvr] WARNING -- Failed to allocate nodeid for API at 172.16.22.91. Returned error: 'Id 111 already allocated by another node.'
2015-11-18 21:01:00 [MgmtSrvr] INFO -- Nodeid 1 allocated for NDB at 172.16.22.22
2015-11-18 21:01:00 [MgmtSrvr] ALERT -- Node 1: Forced node shutdown completed, restarting. Occured during startphase 0. Initiated by signal 6.
2015-11-18 21:01:01 [MgmtSrvr] WARNING -- Failed to allocate nodeid for API at 172.16.22.91. Returned error: 'Id 111 already allocated by another node.'
2015-11-18 21:01:02 [MgmtSrvr] INFO -- Nodeid 2 allocated for NDB at 172.16.22.22
2015-11-18 21:01:03 [MgmtSrvr] ALERT -- Node 2: Forced node shutdown completed, restarting. Occured during startphase 0. Initiated by signal 6.
2015-11-18 21:01:05 [MgmtSrvr] WARNING -- Failed to allocate nodeid for API at 172.16.22.91. Returned error: 'Id 111 already a

 

Changes

Potentially a new MySQL Cluster environment is being setup or a recent Cluster config change has been made.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms