A pitfall I overlooked when upgrading the Aurora version using the Aurora B/G deployment feature.
This is Onikai (@fat47) from the Service Reliability Group (SRG) of the Technology Division.
#SRGThe Service Reliability Group primarily provides comprehensive support for the infrastructure surrounding our media services, focusing on improving existing services, launching new ones, and contributing to open-source software (OSS).
This article is located within SRG.DBWGThe DB Working Group is releasing database-related materials that it provides to the entire company.
I hope this is of some help.
Introduction
PreviouslyVerified articleI created it, but then I had to upgrade the Aurora cluster in the production environment.
I tried using this B/G Deploy feature, so I'd like to share some of the pitfalls (specifications) I encountered.
Traps encountered (specifications)
For details on how the B/G Deploy feature works and its mechanisms, please refer to the article above or the official documentation.
DBパラメータグループIn that case, the parameter changes will be reflected once the creation process is complete.
DBパラメータグループHowever, if you specify a parameter update type that is not Dynamic for the parameter group,
Since it is not applied during generation and the parameter group application is in a "waiting for restart" state,
generatedThe parameters will not be reflected unless you manually restart the Green cluster instance.This is the result.
I overlooked this behavior and ended up switching to a Green cluster that was started with the default parameter group.
This behavior doesn't seem to be mentioned in the official documentation, so please be aware of this.
Reproduction steps
- We will create a cluster using Aurora v1 (5.6).
- Create a parameter group.
binlog_format
- From the "Actions" section of the cluster you created, select "Create Blue/Green Deployment".
- Enter the identifier and specify the parameter group you created earlier.

- After clicking "Create," wait for the status to complete.

- Once the startup is complete, we will check the status of the created Green instance.
- The specified parameter group was in a restart pending state.

- Let's connect to the Green endpoint and check the values.
ROWMIXED- Restart the Green instance to apply the changes.
- After restarting, you can verify that the parameters have been applied.
In conclusion
Cluster upgrades using the B/G Deploy feature are extremely convenient.
However, as mentioned above, there are also specifications that must be thoroughly checked for proper operation.
SRG is looking for new team members.
If you are interested, please contact us here.
