Creating NodeGroup Causes API Node To Crash With Segmentation Fault 6 (INVALID SUB_GCP_COMPLETE_REP) (Doc ID 2025419.1)

Last updated on OCTOBER 25, 2015

Applies to:

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


When attempting to create NodeGroup, all the APIs crash with the following error.

2015-03-31 05:50:22 30797 [Note] table './bets/odds_resulting_wins' opened read only
2015-03-31 05:50:22 [NdbApi] INFO     -- Flushing incomplete GCI:s < 57999776/3
2015-03-31 05:50:22 [NdbApi] INFO     -- Flushing incomplete GCI:s < 57999776/3
gci_hi: 57999814
gci_lo: 2
sender: 1010009
count: 2
bucket count: 1
total buckets: 8
02:51:02 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1454714 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f9c740433c0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...


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