Data Node Fails to Start After Dropping Table With Foreign Key: Forced node shutdown completed. Occured during startphase 0. Initiated by signal 11. (Doc ID 2083957.1)

Last updated on MARCH 08, 2017

Applies to:

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

Symptoms

In MySQL Cluster 7.3 before 7.3.12 and MySQL Cluster 7.4 before 7.4.9, when the following sequence of events occurs:

  1. A data node is shut down; it does not matter whether the data node was stopped on purpose or crashed.
  2. A table with a foreign key is dropped.
  3. The offline data node is started (without --initial).

During the attempt to restart, the data node fails with a segmentation fault.

The error in the cluster log looks like:

 

In general there is no error log entry or trace files for the crash.

Changes

A table with a foreign key was dropped while one or more data nodes were offline.

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