My Oracle Support Banner

SQL Node (mysqld) Process Fails Due To Segmentation Fault (Signal 11) After Restart of the Binlog Thread (Doc ID 2167697.1)

Last updated on MARCH 08, 2017

Applies to:

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

Symptoms

After the binlog thread for the SQL node (mysqld) has been restarted (for example after the node temporarily has been disconnected from the data nodes), the node fails with a segmentation fault (signal 11).

This issue can occur even with binlogging disabled. The reason is that MySQL Cluster uses the binlog thread to communicate schema changes between the SQL nodes, so the binlog thread will always be present when the SQL node is connected to the data nodes.

 

The stack trace vary, but will include something that requires opening tables, for example:

Other traces may occur including attempts to update index statistics.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.