While utilizing a connector to Google Cloud MySQL there was a failover from the primary to the secondary. This required a full re-sync as there is no way to recover.
This not only requires downtime while the sync is running (~4 hours for us) and also costs us a lot because it brings every row into the month.
Submitting a support ticket it appears that there is another option
"For your use-case, a potential workaround would be for you to provide us the new binlog filename and position number, which we would use to manually update the connector "cursor". There would be some downtime in this scenario of about ~30 minutes - 1 hour."
It would nice to have a better way to handle a failover without having to do a full sync. It is just not cost effective.