Last updated on NOVEMBER 23, 2015
Applies to:MySQL Cluster - Version 7.0 and later
Information in this document applies to any platform.
The issue can be reproduced at will with the following steps:
- By mistake, set (change) incorrect values for the config parameters, for a full functional Cluster.
- The set command requires the data node to be restarted with the new config value.
- Some of these changes can prevent the data nodes from starting up. These changes typically requires memory or storage at OS level.
- Now trying to undo (via set or reset) the change done , so that the data node could start, will fail since it requires the data node process to be started.
Set a configuration parameter to an value that makes the Cluster Data node (ndbd/ndbmtd) to fail the restart.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms