Running a Postgres Aurora RDS with one writer and two readers.
One reader is used heavily, but the other is barely used at all according to CloudWatch.
The Laravel application this is connected to points the read host to the reader cluster endpoint so that Aurora can do the balancing internally, but it does not appear to be doing that, instead favoring the 1st reader exclusively.
Is there some misconfiguration in the RDS or something else going on?
Best Answer
We have also faced the same issue and it got resolve after reduced the
DNS TTL
value in ourJava
application.Amazon Aurora for MySQL or PostgreSQL distribute workload between reader nodes as below (From AWS Manual)
In your application check the
DNS TTL
set for the application and adjust it down to 5 seconds.