Data Node not Starting in MySQL Cluster; Error 1501 (Doc ID 1417197.1)

Last updated on MAY 01, 2016

Applies to:

MySQL Server - Version 5.1 and later
MySQL Cluster - Version 6.3 and later
Information in this document applies to any platform.

Symptoms

On : MySQL Cluster when attempting to start the Cluster after a standard network partition issue, the following error occurs.

ERROR
-----------------------
Message: System error, node killed during node restart by other node (Internal error, programming error or missing error message, please report a bug)
Error: 2303
Error data: Killed by node 4 as copyfrag failed, error: 1501


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create Logfile group with very small undo file space.
2. Attempt to start Cluster

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot start the Cluster and bring up all data nodes as the error stops the node from starting.

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