Hello Roshan,
According to this document " To minimize performance impact on the master, while ensuring that changes are never lost, the replica logs the update events, and then performs the updates in order." Therefore, I highly doubt that there is specific task that runs every 4- 5 minutes to keep both instances synced, but rather in seconds per order of each operation . You may verify that by checking the replication lag metrics (seconds behind master).
As for stopping/pausing the failover replica, it is not currently possible. As you mentioned, you would have to delete it, and this would render your master not to be configured with high availability. If you choose to recreate the replica, you may check this guide for quick configurations. I hope this helps
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/4619340a-7d47-4a12-9e78-062e4e24282a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment