1 Answer
- Newest
- Most votes
- Most comments
0
I was able to remove the "stuck" upgrading cross-region replica by making an AWS CLI call to promote the read replica to be stand-alone. The CLI was required as the "Promote" menu option was disabled.
aws rds promote-read-replica-db-cluster --db-cluster-identifier my-cross-region-cluster-name
Once this completed, I was then able to delete the reader instance which then allowed the cluster to delete as well. I can now upgrade the origin cluster to MySQL 5.8 and then create a new cross-region replica AFTER the primary cluster has finished upgrading.
This does not technically tell how to "fix" the stuck upgrade, but is a work-around. If this had been our primary cluster that was stuck then it would require restoring from a snapshot.
answered 2 years ago
Relevant content
- asked 3 years ago
- asked 10 months ago
- asked 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago