MySQL Cluster + Forced Node Shutdown + Signal 11 + Error 4010 + Error 6000 + IndexMemory or DataMemory at least 2000 MB (Doc ID 1354751.1)

Last updated on JUNE 29, 2016

Applies to:

MySQL Cluster - Version 7.1 to 7.1 [Release 7.1]
Information in this document applies to any platform.

Symptoms

When trying to start the cluster, it crashes with the following error:

ERROR 1297 (HY000): Got temporary error 4010 'Node failure caused abort of transaction' from NDBCLUSTER


and the following errors are in the error log:

[ndbd] INFO -- Received signal 11. Running error handler.
[ndbd] INFO -- Signal 11 received; Segmentation fault
[ndbd] INFO -- ndbd.cpp
[ndbd] INFO -- Error handler signal shutting down system
[ndbd] INFO -- Error handler shutdown completed - exiting
[ndbd] ALERT -- Node 1: Forced node shutdown completed. Initiated by signal 11. Caused by error 6000: 'Error OS signal received(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'.



Note: The errors actually encountered might be different than the above

Changes

The issue may be encountered after making either one of the following changes:


In both cases, the issue will only be encountered if the IndexMemory and/or DataMemory options are set to "large" values. A value of 2000M or larger for the IndexMemory or 8G for the DataMemory is known to trigger the problem.


Note that MySQL Cluster 7.1.15 and 7.1.15a are not the same version. 7.1.15a is not included in the above.

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