- Newest
- Most votes
- Most comments
Once it is created in a multi-az, you will have one reader and one writer as shown below
When you create one additional reader on top of it then it will be like below
However when you create a replica and select multi-az on the regional cluster it will have a replica cluster with one writer and one reader and if you do no multi-az then it will have a replica cluster with writer as shown once created. Then in case fail over you can move application from current primary to the cross-region replica by promoting your cross-region replica to be the new primary from the Amazon RDS console.
when using multi-az and once it is done creating
when using no multi-az and once it is done creating
You have an RDS MySQL instance that is replicating to an RDS Aurora Cluster. The cluster has two reader nodes. When you promote that cluster one of the reader nodes will flip to a writer node.
"When you promote that cluster one of the reader nodes will flip to a writer node." Super clear - that is indeed the case after the cluster was done setting up.
Thanks
Relevant content
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Nice, that clears up the "Multi-AZ" colum with "x zones". So all instances, writer or reader, are counted into the nr of zones, acting as "Multi-AZ".
Thanks!