Data Node Fails To Start During Memory Allocation: "Forced node shutdown completed. Occured during startphase 0. Caused by error 6050: 'WatchDog terminate, internal error or massive overload ..." (Doc ID 2131776.1)

Last updated on FEBRUARY 05, 2019

Applies to:

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

Symptoms

When starting a data node it fails due to the WatchDog terminating the node while allocating memory in startphase 0. From the data node's error log:

Changes

The issue may start to happen after changing the configuration in such a way that more memory is required by the data node. However this is not a requirement.

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Data Node Fails To Start During Memory Allocation: "Forced node shutdown completed. Occured during startphase 0. Caused by error 6050: 'WatchDog terminate, internal error or massive overload ..." (Doc ID 2131776.1)

Applies to:

Symptoms

Changes

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!