Bug #65819 MySQL Cluster dies right after slave start command

• Submitted: 5 Jul 2012 8:43
• Modified: 14 Aug 2019 19:22
• Reporter: Bohdan Sydor
• Status: Not a Bug
• Category: MySQL Cluster: Replication
• Severity: S1 (Critical)
• Version: 7.2.6
• OS: Linux (Ubuntu x86_64)
• Assigned to: MySQL Verification Team
• CPU Architecture: Any
• Tags: DbtupRoutines, ndbrequire, replication

[5 Jul 2012 8:43] Bohdan Sydor

Description:
We have two MySQL Clusters in two sites, and are trying to establish asynchronous master--slave SQL replication between them. The slave cluster dies right after the `slave start' command. The messages in the error log on the data node look like the following:

Time: Thursday 5 July 2012 - 10:12:20
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error, programming error or missing error message, please report a bug)
Error: 2341
Error data: DbtupRoutines.cpp
Error object: DBTUP (Line: 728) 0x00000006
Program: ndbd
Pid: 8099
Version: mysql-5.5.22 ndb-7.2.6
Trace: /mysql-cluster/ndb-data//ndb_26_trace.log.1 [t1..t1]
***EOM***

How to repeat:
- Reset the cluster (clear all data in NDB and MySQL data directories, start ndb_mgm and ndb processes)
- Restore data from a backup copy on slave (using ndb_restore)
- Get the epoch value on slave, determine the binlog and position on master
- Change master settings on slave
- Start the replication

[14 Aug 2019 19:22] MySQL Verification Team

Hi Bohdan,

This is not a bug but incorrect configuration of the cluster.

all best
Bogdan