How To Recover Group Replication/InnoDB Cluster Data Inconsistencies Which All Secondaries Are Out-Of-Sync From Primary In Single-Primary Mode
(Doc ID 2774365.1)
Last updated on JULY 18, 2021
Applies to:MySQL Server - Version 8.0 and later
Information in this document applies to any platform.
In certain cases, it is possible that only the source, the primary has a correct data, and the secondary nodes have corrupted data. By design, secondaries should have identical data to the primary node with a little delay because of its asynchronous characteristics; all secondaries catch up with the primary continuously through replication. However, inconsistency in their data can happen due to various reasons:
- Operation mistakes
- Bugs like <Bug 31869146>, which the GRANT statement causes different results between the source/primary and the replica/secondary.
- Physical data corruption.
This document describes how to fix the situation where all secondary nodes have inconsistent data.
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
|Full Backup and Restore|
|Cloning Recovery Method|