Our DB Cluster is Down during Minor Version Upgrade

Question

Hello there,
Our DB Cluster went down during minor version upgrade. Can Somebody help us to resolve this issue? 
Status is Still Upgrading
Current Version: 8.0.mysql_aurora.3.05.2
Target Version: 8.0.mysql_aurora.3.07.1

AWS-User-0417258 · Accepted Answer

Finally, the cluster is back after an hour of downtime. When we tested with a snapshot of the same instance type(db.r6g.2xlarge) two days ago, it worked without any issues, and the upgrade completed within seven minutes without any downtime. Today it's behavior is totally odd. Tomorrow, they'll probably create a support ticket asking us to increase memory or suggest other unnecessary actions.

And Thanks to your support team for suggesting we pay extra for premium support to handle the issues caused by you. YOU RELEASE MORE BUGS AND WE PAY EXTRA TO RESOLVE THOSE.

re:Post Agent · Answer

I apologize for the issue you're experiencing with your DB Cluster during the minor version upgrade. While minor version upgrades are generally designed to be less disruptive, occasional issues can occur. Here are some steps and information to help address your situation:

1. First, it's important to note that minor version upgrades typically don't require downtime, especially with the zero-downtime patching (ZDP) feature. However, the upgrade process can take some time, particularly for larger clusters.

2. The "Still Upgrading" status you're seeing is not uncommon during the upgrade process. The duration can vary depending on the size of your cluster and the specific changes in the new version.

3. If the upgrade has been stuck for an unusually long time (several hours), you may want to contact AWS Support for assistance. They can provide specific insights into your cluster's status and any potential issues.

4. For future upgrades, consider the following best practices:
   - Perform upgrades during periods of low traffic, which you can identify using Performance Insights.
   - Use the AWS SDKs with exponential backoff and jitter for better handling of API requests during the upgrade.
   - For immediate switchover to an upgraded cluster, you might want to consider using Amazon Aurora Blue/Green Deployments in the future.

5. Once the upgrade is complete, verify that all instances in your cluster have been updated to the new version.

6. If you're using an Aurora Global Database, remember to upgrade all secondary clusters before upgrading the primary cluster in future upgrades.

If the issue persists or you need immediate assistance, I strongly recommend reaching out to AWS Support. They can provide real-time monitoring and support for your specific cluster situation.  
**Sources**  
[Upgrading the minor version or patch level of an Aurora MySQL DB cluster - Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html)  
[Performing a minor version upgrade - Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MinorUpgrade.html)  
[Upgrading Aurora MySQL by modifying the engine version - Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.ModifyEngineVersion.html)

Our DB Cluster is Down during Minor Version Upgrade

Add your answer

Relevant content