Global: Conflict with timezone refresh and replica startup causes replication failure for Google Cloud SQL

The issue with Google Cloud SQL is believed to be affecting a very small number of projects and our Engineering Team is working on it. If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved. No further updates will be provided here. We thank you for your patience while we're working on resolving the issue.

Summary: Global: Conflict with timezone refresh and replica startup causes replication failure for Google Cloud SQL Description: Our engineering team continues to work on the mitigation of the issue. We will provide an update by Monday, 2022-08-29 17:30 US/Pacific with current details. Diagnosis: Customers may experience replication failure after maintenance on replica, if the master instance is busy with INSERTs/UPDATEs on tables with timestamp column and session timezone is set to other than SYSTEM. Workaround: In most cases, internal automation should resolve the issue within 30 minutes. If internal automation does not resolve the issue, or if it is critical to restore service sooner, customers can DISABLE REPLICA and ENABLE REPLICA on their replica instances to fix the replication failure. Please refer to documentation [1] [1] https://cloud.google.com/sql/docs/mysql/replication/manage-replicas

Summary: Global: Conflict with timezone refresh and replica startup causes replication failure for Google Cloud SQL Description: Our engineering team continues to work on the mitigation of the issue. We will provide an update by Monday, 2022-08-29 15:30 US/Pacific with current details. Diagnosis: Customer may experience replication failure on the new CSA rollout on replica, if the master instance is busy with INSERTs/UPDATEs on tables with timestamp column and session timezone is set to other than SYSTEM. Workaround: Customers can DISABLE REPLICA and ENABLE REPLICA on their replica instances to fix the replication failure. Customers can use gcloud command to enable replication again on a failed replica server gcloud sql instances patch REPLICA_NAME --enable-database-replication

Summary: Global: Conflict with timezone refresh and replica startup causes replication failure for Google Cloud SQL Description: Our engineering team continues to work on the mitigation of the issue. We will provide an update by Monday, 2022-08-29 13:30 US/Pacific with current details. Diagnosis: Customer may experience replication failure on the new CSA rollout on replica, if the master instance is busy with INSERTs/UPDATEs on tables with timestamp column and session timezone is set to other than SYSTEM. Workaround: Customers can DISABLE REPLICA and ENABLE REPLICA on their replica instances to fix the replication failure. Customers can use gcloud command to enable replication again on a failed replica server gcloud sql instances patch REPLICA_NAME --enable-database-replication

Summary: Global: Conflict with timezone refresh and replica startup causes replication failure for Google Cloud SQL Description: Our engineering team is currently investigating the issue and working on mitigation steps. We will provide an update by Monday, 2022-08-29 13:00 US/Pacific with current details. Diagnosis: Customer may experience replication failure on the new CSA rollout on replica, if the master instance is busy with INSERTs/UPDATEs on tables with timestamp column and session timezone is set to other than SYSTEM. Workaround: Customers can DISABLE REPLICA and ENABLE REPLICA on their replica instances to fix the replication failure. Customers can use gcloud command to enable replication again on a failed replica server gcloud sql instances patch REPLICA_NAME --enable-database-replication

Summary: Global: Conflict with timezone refresh and replica startup causes replication failure for Google Cloud SQL Description: Our engineering team is currently investigating the issue and working on mitigation steps. We will provide an update by Monday, 2022-08-29 12:00 US/Pacific with current details. Diagnosis: Customer may experience replication failure on the new CSA rollout on replica, if the master instance is busy with INSERTs/UPDATEs on tables with timestamp column and session timezone is set to other than SYSTEM. Workaround: Customers can DISABLE REPLICA and ENABLE REPLICA on their replica instances to fix the replication failure. Customers can use gcloud command to enable replication again on a failed replica server gcloud sql instances patch REPLICA_NAME --enable-database-replication

Summary: Global: Conflict with timezone refresh and replica startup causes replication failure for Google Cloud SQL Description: We are experiencing an issue with Google Cloud SQL. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2022-08-29 11:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Customer may experience replication failure on the new CSA rollout on replica, if the master instance is busy with INSERTs/UPDATEs on tables with timestamp column and session timezone is set to other than SYSTEM. Workaround: Customers can DISABLE REPLICA and ENABLE REPLICA on their replica instances to fix the replication failure.