Select Language:
If you’re planning to upgrade your Aurora MySQL cluster from a db.r6g.large to a db.r6g.12xlarge, it’s important to understand that this is a vertical scaling process. It involves changing the instance size rather than updating the database engine version, which makes the process simpler. To ensure everything goes smoothly, here are some key steps you should follow.
First, check your current parameter groups. If you’re using a custom parameter group, review all parameters to make sure they work well with the larger instance size. Some parameters may need to be adjusted to match the increased resources such as memory and CPU. If you’re using the default parameter group, it will automatically apply to the new instance.
Next, pay attention to memory usage. Monitor the FreeableMemory metric in CloudWatch on your existing instance. Since you’re scaling up, the new instance will have more memory, but understanding your current memory use can help with planning and troubleshooting.
It’s also a good idea to record key metrics before the upgrade to compare after the change. Capture data on CPU utilization, FreeableMemory, database connections, read and write IOPS and latency, throughput, buffer cache hit ratio, and commit latency. These metrics will give you a clear picture of your database’s performance before and after the upgrade.
Before making the switch, confirm that automatic backups are enabled, and take a manual snapshot of your database. This provides a recovery point if needed.
If possible, test the upgrade in a non-production environment first. This helps verify how your application performs with the larger instance size without risking your main environment.
Since you have scheduled downtime, plan to perform this upgrade during your maintenance window. The process involves a brief outage while the instance class is being changed, but it helps ensure a smooth transition.
By following these steps, you can upgrade your Aurora MySQL cluster effectively and minimize any potential issues. For detailed instructions and additional guidance, refer to the official AWS documentation on in-place upgrades and best practices for database upgrades.
ChatGPT
Perplexity
Gemini AI
Grok AI
