Re-Slaving a Crashed MySQL Master Server in Semisynchronous Replication Setup
Scalegrid
DECEMBER 9, 2019
However, when the crashed master comes back, you may find that it has transactions that are not present in the current master (which was previously a slave). However, discarding a server like this is expensive and inefficient. Why Is It Important to Detect Extra Transactions on the Recovered Master? In a MySQL 5.7
Let's personalize your content