About SRGTechnical ArticlesRecruitment Information
About SRGTechnical ArticlesRecruitment Information
HOME/Technical Articles/A trap that was overlooked when upgrading the Aurora version using the Aurora B/G deployment feature

A trap that was overlooked when upgrading the Aurora version using the Aurora B/G deployment feature

This is Oniumi (@fat47) from the Service Reliability Group (SRG) of the Technology Headquarters.
#SRG(Service Reliability Group) is a group that mainly provides cross-sectional support for the infrastructure of our media services, improving existing services, launching new ones, and contributing to OSS.
This article is located in SRGDBWGWe will publish materials regarding the database provided by the DB Working Group for the entire company.
I hope this helps in some way.
 

Introduction

The B/G Deploy feature for RDS and Aurora was announced at re:Invent 2022 last year.Announced featuresis.
PreviouslyVerified articlesI created a new Aurora cluster and then upgraded it.
I tried using this B/G Deploy function, and I'd like to share with you some of the pitfalls (specifications) I encountered.
 

Trap encountered (specifications)

For information on how the B/G Deploy function works, please refer to the article above or the official documentation.
 
DBパラメータグループ
In this case, the parameter changes will be reflected once creation is complete.
DBパラメータグループ
However, if the parameter update type of the parameter group is specified as something other than Dynamic,
It is not applied at the time of generation and the application of the parameter group is in the "waiting for restart" state,
GeneratedThe parameters will not be reflected unless you manually restart the Green cluster instance.It will be.
 
This behavior was overlooked, resulting in switching to a Green cluster that had been launched with the default parameter group.
Please note that this behavior does not appear to be described in the official documentation.

Steps to reproduce

  1. Create a cluster with Aurora v1(5.6).
  1. Create a parameter group.
    1. binlog_format
  1. From the Actions menu for the cluster you created, select Create Blue/Green Deployment.
  1. Enter the identifier and the parameter group you created earlier.
      2.  
  1. Click Create and wait for the status to complete.
  1. Once the startup is complete, check the status of the created Green instance.
    1. The specified parameter group was pending reboot.
  1. Let's connect to the Green endpoint and check the value.
      2. ROW
      MIXED
  1. Restart the Green instance for the changes to take effect.
  1. After rebooting, you can see that the parameters have been applied.
     

    Conclusion

    Cluster upgrades using the B/G Deploy function are very convenient.
    However, as there are specifications such as those introduced here, be sure to thoroughly check that it works.
     
    SRG is looking for people to work with us. If you're interested, please contact us here.