- Más nuevo
- Más votos
- Más comentarios
This is indeed strange behavior, Are you using IAM for authentication ? I am really curious if your connections are getting pinned and every call to the database has to get a new connection. There are couple of metrics that you can monitor that might give you some idea where the delay is coming from, DatabaseConnections and DatabaseConnectionsCurrentlyBorrowed to get the number of connections and connections in use, and DatabaseConnectionsBorrowLatency, DatabaseConnectionsCurrentlySessionPinned. These are available in cloudwatch https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-proxy.monitoring.html
Hi Devinder,
We don't use IAM for authentication. It's username/password. I believe RDS Proxy stores this in AWS Secrets?
Thanks, I'll check out those metrics.
I've added some metric screenshots if it helps.
Hi! Did you get a resolution for your issue?
These all look good. I would suggest please open a ticket with support as they will have access to logs and all and can help troubleshoot the issue.
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace un año
What language & db client in your web app are used to make these db queries?
JasonF, did you ever manage to fix your issue? We have a similar behavior where DB queries take roughly twice as long since we started talking to our aurora MySQL (1.x for us) through an RDS proxy.
Hi, similar to the above, we're experiencing the same issue - did you find a solution?
Anthony: on our side we didn't find a solution. While the doubling of latency seemed huge, the impact on our SLOs (and hence, on our users) was low, so we decided to continue using the proxy.