Restarting a Machine Running SQL or Data Nodes Causes a Timeout Preventing NodeID Allocation
Last updated on MARCH 24, 2017
Applies to:MySQL Cluster - Version 6.3 to 7.1 [Release 6.3 to 7.1]
Information in this document applies to any platform.
After a reset of a machine running Data Node(s) and/or SQL/API node(s), it is possible that nodes can not get a node ID when started again.
Retrying to start the processes usually works and a node ID is allocated.
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