1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
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.
답변함 2년 전
관련 콘텐츠
- 질문됨 7년 전
- AWS 공식업데이트됨 2년 전
- AWS 공식업데이트됨 일 년 전