1 Answer
- Newest
- Most votes
- Most comments
0
Hi.
If you check Amazon Aurora connection management it gives the answer you are looking for. Read operations using the reader endpoint only loadbalance between replica instances:
Use the reader endpoint for read operations, such as queries.
By processing those statements on the read-only Aurora Replicas,
this endpoint reduces the overhead on the primary instance.
It also helps the cluster to scale the capacity to handle simultaneous
SELECT queries, proportional to the number of Aurora Replicas in
the cluster.
The reader endpoint load-balances connections to available
Aurora Replicas in an Aurora DB cluster.
It doesn't load-balance individual queries.
Relevant content
- asked 10 months ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 3 years ago
Thank's, it's very clear.
Do you happen to know what strategy aurora uses to balance between all read replicas? Does it take cpu usage into account for instance?
Hey
I think it's only uses connection count, that is how I interpret the documentation at least.
Hi,
Aurora Reader endpoint uses DNS Round Robin method in order to distribute new connections across Readers. So if clients have DNS cache, connection will go to specific (cached ip address) Reader while cache is active.