Amazon Aurora MySQL Improves Availability of Read Replicas
Amazon Aurora MySQL-Compatible Edition now maintains read availability through writer node restarts. Previously, when a writer node restarted, all nodes in an Aurora MySQL cluster restarted as well. With today’s launch, reader nodes will continue to serve read requests during a writer node restart, improving read availability in the cluster.
Amazon Aurora MySQL-Compatible Edition now maintains read availability through writer node restarts. Previously, when a writer node restarted, all nodes in an Aurora MySQL cluster restarted as well. With today’s launch, reader nodes will continue to serve read requests during a writer node restart, improving read availability in the cluster.
A planned writer node restart is commonly done to apply static parameters such as enabling and disabling binlog. Maintaining read availability through these restarts helps reduce the impact of making changes to writer configurations. In addition, availability is improved in the event of a failover, where reader nodes will remain available and reconnect to the newly promoted writer. This functionality is available by default on Aurora MySQL 2.10 and above. Read the Aurora MySQL documentation to learn more.
Amazon Aurora combines the performance and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases. It provides up to five times better throughput than standard MySQL together with increased scalability, durability, and security.