About SRGArticlesRecruitment Information
About SRGArticlesRecruitment Information
HOME/Articles/A trap to be overlooked when upgrading Aurora version with Aurora B/G deployment function

A trap to be overlooked when upgrading Aurora version with Aurora B/G deployment function

This is Oniumi (@fat47) from the Service Reliability Group (SRG) of the Technology Headquarters.
#SRG(Service Reliability Group) mainly provides cross-sectional support for the infrastructure of our media services, improving existing services, launching new ones, contributing to OSS, etc.
This article is located in SRGDBWGWe will publish materials regarding the database that the (DB Working Group) provides to 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 this, but then I upgraded my production Aurora cluster.
I tried using this B/G Deploy function, so 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 update type of the parameter in the parameter group is not Dynamic,
Since it is not applied at the time of generation and the application of the parameter group is in the "pending restart" state,
GeneratedThe parameters will not be reflected unless you manually restart the Green cluster instance.It will be.
 
This behavior was overlooked and we ended up switching to a Green cluster that had been launched with the default parameter group.
Please note that this behavior is not 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 an 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 as introduced here, be sure to thoroughly check that it works.
     
    SRG is looking for people to work with us. If you are interested, please contact us here.