How to failback to Original Writer instance after Upgrade
Currently i have 1 writer and 2 reader instance in AuroraDB. When I was trying to change the instance write instance type to larger instance, aurora automatically promoted a reader instance to writer. But after the upgrade finish, the original writer instance stayed as reader instance. Is there a way to have a automatic failback to the original writer after the upgrade is completed?
Unfortunately, no. The upgrade is designed to failover first to reduce downtime. The readers and write should be on the similar instance class in Aurora cluster. You can try either of these:
- Upgrade your new writer now, which would automatically failover to give your original configuration with both instances to new instance sizing.
- Manually failover the cluster to switch the configuration from console, CLI or API call, and then you can upgrade reader without a failover.
How to failback to Original Writer instance after Upgradeasked 2 months ago
Unable to configure Multi AZ deployment for existing Aurora MySQLAccepted Answerasked 2 months ago
change EC2 parameters (cores, RAM) after I have installed a GUI and some softwaresasked 4 months ago
RDS MySQL 5.6 > 5.7 Update Issuesasked 3 months ago
Cloned Instance Redirecting to Original Instanceasked 3 years ago
Aurora cluster requires a system update?asked 3 years ago
CodeDeploy just recognizes IAM instance profiles after restarting agentAccepted Answerasked 3 years ago
Is Aurora sure distribution Reader request across the entire Reader instance?Accepted Answerasked a month ago
Aurora event You may want to increase the provisioned storageasked 9 months ago
How to attach EBS volume from original EC2 instance to a new EC2 instance?asked 14 days ago