Zero data loss auto failover and sync old primary as replica without need of rebuild


We want to enable auto failover with zero data loss and we want to avoid replica rebuild to resync the old primary without compromising with data consistently

Whats best solution with percona mysql server

I read this document but it does not talk about syncing our primary back as primary without rebuild

Hey @Sanjay_Sheoran ,

could you please share more here? Would be great to see some graphical vizualization of what are you trying to do.

If I understand it correctly, you want to fail back, after the failover to your other site happened. It might require some additional steps as reconfiguring your old primary as secondary to your active cluster.

I want to reconfigure old primary as replica without any data loss/inconsistency after auto failover

Hello @Sanjay_Sheoran,
You have not specified if this is async replication, or Percona XtraDB Cluster, or Group Replication?

We have percona SQL Server with semi sync replication and setup will be one primary and semi sync replication in same region

Now we want to make sure we can achieve zero data loss plus sync the replication back with out need of rebuild and make sure data is also consistent

Please note that semi-sync replication is deprecated in 8.0 and may be removed in future releases.

You will need to configure source/source replication. This is where node1 is source and node2 is replica, but also node2 is source and node1 is replica.

For the “auto failover” part, you will need to implement a failover tool like HAProxy or ProxySQL to redirect traffic to node2 if node1 goes offline.

Thank You, do you have any documentation for semi sync deprecation

“Please note that semi-sync replication is deprecated in 8.0 and may be removed in future releases.”

Percona XtraDB Cluster, or MySQL/Percona Group Replication

Hi @matthewb

Can you please share a reference to doc for “semi sync replication deprecation” ?
This is crucial for us in deciding on next steps.

Hi @Chanakya,
I could not find any documentation on the deprecation. I asked those that shared the info with me and it came from a private conversation at Percona Live last year with some MySQL engineers. As such, I’m no longer mentioning this and you should continue until such a time it is noted in the release notes.

Thank you @matthewb We will proceed with experimenting it.