How to failback to Original Writer instance after Upgrade
0
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?
Topics
asked 2 months ago1 views
1 Answers
0
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.
answered 2 months ago
Relevant questions
How to failback to Original Writer instance after Upgrade
asked 2 months agoUnable to configure Multi AZ deployment for existing Aurora MySQL
Accepted Answerasked 2 months agochange EC2 parameters (cores, RAM) after I have installed a GUI and some softwares
asked 4 months agoRDS MySQL 5.6 > 5.7 Update Issues
asked 3 months agoCloned Instance Redirecting to Original Instance
asked 3 years agoAurora cluster requires a system update?
asked 3 years agoCodeDeploy just recognizes IAM instance profiles after restarting agent
Accepted Answerasked 3 years agoIs Aurora sure distribution Reader request across the entire Reader instance?
Accepted Answerasked a month agoAurora event You may want to increase the provisioned storage
asked 9 months agoHow to attach EBS volume from original EC2 instance to a new EC2 instance?
asked 14 days ago