2回答
- 新しい順
- 投票が多い順
- コメントが多い順
1
There is a known documented limitation with Amazon RDS MySQL that also impacts RDS MariaDB. We have seen this resolved by doing the following:
- Initiate the Blue/Green deployment, selecting the existing version of the database. Again, do not select a version upgrade, you will do this later.
- Complete the Blue/Green deployment initialization until status is available for all resources
- Now perform and in-place upgrade to the Green database instance, selecting your desired engine, and associating parameter and option groups
- Continue evaluating and testing your Green database and proceed with the Blue/Green deployment process
Give that a try and let us know how it goes.
回答済み 6ヶ月前
-1
Yes, this is a known documented limitation. We recommend that you remove the options group and then create Blue/Green Deployments. If you need further assistance, please contact us through our regular support channel.
回答済み 6ヶ月前
Meaning remove the options group for the blue database? That is a production database.
The known limitations cover RDS My SQL but not MariaDB. Should I be understanding that this also applies to RDS MariaDB then?
I have basic support so can't open a technical ticket :(
But is it possible to perform the upgrade on the MariaDB instance after the Blue/Green is started?
Tried this and it worked. Was a bit of a messy process but I was able to upgrade the read replica first and then the active db both on the green instance. I now have the 10.6.8 DB running as a green deployment and I am testing. Thanks for the help. Would be good to update the documentation on this.
Hi, I did as indicated here, but now the coordination between the green and blue databases has stopped. I have created some new records in the blue database, and they are not present on the green one. In my case my database is MySql, the blue one is 5.7.42 and the green, I upgraded it to 8.0.35 (after creating the blue/green deployment).