Data Node Shuts Down Unexpectedly Shortly After Other Node Failure Due to GCP Stop

(Doc ID 2378948.1)

Last updated on APRIL 05, 2018

Applies to:

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


In a cluster, a host stops responding such that the global checkpoint (GCP) lags start to increase. This can for example happen in connection with a disk hardware issue where the data node will still send heartbeats for a while. Eventually the data node on the affected host is killed, for example due to missed heartbeats. A very short time after, a healthy node is shut down due to a GCP stop:




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