1 Answer
- Newest
- Most votes
- Most comments
0
According to the documentation, Using the reader endpoint:
"The reader endpoint load-balances connections to available Aurora Replicas in an Aurora DB cluster. It doesn't load-balance individual queries. If you want to load-balance each query to distribute the read workload for a DB cluster, open a new connection to the reader endpoint for each query."
Relevant content
- Accepted Answerasked 2 months ago
AWS OFFICIALUpdated 3 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
yes, thank for you comment. I connect using Reader endpoint of Cluster. but i see when 2 Reader instances db.r5.large are available before,that CPU reaches >99%, the request is still not being loaded to the Reader instance db.r5.4xlarge I just added.
So, new connections are not being load balanced?
Yes, That's right. I noticed the request pointed to the old instance instead of the new instance. so my system was paralyzed because the request didn't reach the new instance. What do you think about this, do I need to open case support with AWS Support?
Yes, if new connections are not being balanced correctly, I would open a support case.