By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

RDS MariaDB Blue/Green Deployment: Invalid configuration

0

Currently completing a Blue/Green deployment to facilitate MariaDB major version upgrade on RDS. Upgrading from 10.3 to 10.6. Existing Blue database has what appears to be a non-default option group, which may be the root cause of issues. The actual instance successfully provisioned, but the blue/green deployment itself is stuck in invalid configuration state. I should also note that the instance did not upgrade successfully or select new parameter group.

Are there any known issues related to MariaDB Blue/Green with major version upgrade? How should I go about identifying root cause?

I did locate this error: Current Option Group is non-default. You need to explicitly specify a new Option Group in this case (default or custom)

This is causing the DB upgrade to fail, but from what I can tell there is no way to select a different option group blue/green deployments.

Topics
Migration & ModernizationAnalyticsDatabase
Tags
Amazon Relational Database ServiceMariaDB
Language
English
mindcycledev
asked 6 months ago2127 views
2 Answers
1
Accepted Answer

There is a known documented limitation with Amazon RDS MySQL that also impacts RDS MariaDB. We have seen this resolved by doing the following:

  1. Initiate the Blue/Green deployment, selecting the existing version of the database. Again, do not select a version upgrade, you will do this later.
  2. Complete the Blue/Green deployment initialization until status is available for all resources
  3. Now perform and in-place upgrade to the Green database instance, selecting your desired engine, and associating parameter and option groups
  4. 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.

AWS
samwardbiddleaws
answered 6 months ago
  • mindcycledev
    6 months ago

    But is it possible to perform the upgrade on the MariaDB instance after the Blue/Green is started?

  • mindcycledev
    6 months ago

    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.

  • MsCopernic
    3 months ago

    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).

-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.

AWS
AWS-RDS-Product Manager
answered 6 months ago
  • mindcycledev
    6 months ago

    Meaning remove the options group for the blue database? That is a production database.

  • mindcycledev
    6 months ago

    The known limitations cover RDS My SQL but not MariaDB. Should I be understanding that this also applies to RDS MariaDB then?

  • mindcycledev
    6 months ago

    I have basic support so can't open a technical ticket :(

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content