My Oracle Support Banner

MySQL Cluster: Slave running with ndb_log_orig or ndb_log_apply_status Enabled Has orig_epoch = 0 for Replicated Events in mysql.ndb_binlog_index; Duplicate Epoch (Doc ID 1539059.1)

Last updated on FEBRUARY 03, 2019

Applies to:

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

Symptoms

With ndb_log_orig and/or ndb_log_apply_status enabled, sometimes orig_epoch in the ndb_binlog_index table is 0 for events replicated to the mysqld instance. When this happens the epoch for the row is duplicated. For example:

 

Changes

The issue can start to occur with one or more of the following 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!


In this Document
Symptoms
Changes
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.