-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Be more verbose about connecting to the read-only endpoint of an aurora RDS instance. #456
Comments
Hi @ls-pieter-vanisacker, thank you for reaching out. In the event of a failover, the driver will attempt to connect to other instances in the cluster by iterating through the instances 2 at a time and attempting connections. If one connection succeeds first, the driver will return that connection and stop the other attempt. This instance may be a writer connection. This is what we meant by "a faster connection". You can set the the |
Perfect, thanks for the quick feedback! |
Describe the issue
The doc states that connecting to a RO endpoint can result in connections being created to the RW instance in failover situations.
Can you elaborate a bit more on what the logic is? What defines
a faster connection
?We're currently using this driver and see an occasional connection of our connection pool going to the RW instance although we're using the RO endpoint.
And since our RW instance is heavily loaded some of the queries just time out.
I've been trying to replicate this in an isolated test but haven't been able to do so yet.
Links
https:/awslabs/aws-mysql-jdbc#connection-url-descriptions
The text was updated successfully, but these errors were encountered: