If a slave fails, applications connected to the slave can connect to another slave and continue to operate.
When the slave comes up again, it will resynchronize with the master and be available to the applications.
Depending on how long the slave is lagging behind, ClusterControl™ will either resynchronize the missing transactions or
delete the old data and provision the slave from scratch.
At this point, the Replication cluster has been restored to its original topology.
Please sign in to leave a comment.