1 Answer
- Newest
- Most votes
- Most comments
1
Hi,
Thank you so much for asking your question.
Yes, when you execute DDL changes on the Writer instance of your Aurora MySQL cluster, those changes are automatically and instantly propagated to all Reader instances in the cluster. This is one of the key benefits of Aurora's architecture.
However, there are a few important points to consider(Following consideration is not Aurora MySQL specific):
- Always test DDL changes in a non-production environment first
- Monitor the replication lag during DDL operations
- Some DDL operations require table locks which can block reads and writes
- It's recommended to perform DDL changes during off-peak hours to minimize impact. Use Aurora's fast cloning feature to test DDL changes if needed
- Please also refer MySQL document: https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl-operations.html
- DDL operations can be resource-intensive
- They may cause increased CPU, memory, and I/O usage and Temporary tables might be created during the process
- Large tables might require significant temporary space during alterations
I hope this might help.
Relevant content
asked 2 years ago
Thanks for your quick response. We ran the DDL in test cluster created from prod cluster snapshot, with only one instance to check how long it would take, but agree we should have tested with at least one writer, one reader. Anyway our changes are not going to take long and its a planned outage anyway.