My Oracle Support Banner

How to Reset MySQL Slave Replication without Full BDA Cluster Downtime (Doc ID 2152683.1)

Last updated on APRIL 27, 2019

Applies to:

Big Data Appliance Integrated Software - Version 4.5.0 and later
Linux x86-64

Goal

The goal is to reset MySQL slave replication without full cluster downtime.

If the MySQL master is healthy, and you want to restore MySQL replication on the slave without full cluster downtime follow this note.

If the MySQL master has stopped generating binary log files and consequently the MySQL slave does not have replication turned on or if the MySQL slave does not have replication turned on and due to the size of the databases taking downtime and copying the files is preferred see: How to Restore A MySQL Master Which Has Stopped Generating Binary Log Files and/or Reset MySQL Slave Replication With Cluster Downtime on Oracle Big Data Appliance (Doc ID 2237773.1).

For reference see the MySQL 5.6 documentation.

Solution

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
Goal
Solution
 Overview
 Known Issues
 BDA MySQL slave replication FAQ
 Verify the MySQL master/slave hosts.
 Determine if MySQL slave replication is on
 Steps to reset MySQL slave replication 
 Prerequisites
 Detailed Steps
 Verification that MySQL slave replication is reset
 Cleanup on the MySQL slave
References

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