Reputation: 3
I wanted to create in Amazon RDS the following topology: master -> slave -> slave. But this topology isn't possible in Amazon RDS. I'll appreciate if somebody can explain if I'll be able to create this kind of slaves with a replication from Amazon RDS (a master) to Aurora DB cluster when an Aurora master will replicate to slave of this "cluster"? Do this topology have additional limitations or cons?
Upvotes: 0
Views: 476
Reputation: 3757
With Aurora, you can have up to 15 read-replicas (slave in your terminology). For those read replicas, you define order of priority. In case that writer (in your terminology master) fails, first read-replica, by the order of priority is promted to writer (master), and other read replicas remain what they were. In the meantime, new RDS instance will be booted automatically with all the data, and will have a position of read-replica.
From your explanation, I believe that this does exactly what you want, when you set 1 writer and 2 read-replicas.
Upvotes: 1
Reputation: 882
Aurora will have primary instance (in your term master) which can handle both read/write operations to DB, while others are "read replicas" that are used only for read operations (not write operations)
Upvotes: 0