Skip to content
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

Would it work with SRV records? #1166

Closed
gaurav517 opened this issue Feb 20, 2023 · 1 comment
Closed

Would it work with SRV records? #1166

gaurav517 opened this issue Feb 20, 2023 · 1 comment
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: question Request for information or clarification.

Comments

@gaurav517
Copy link

Question

Would it work with srv schemas in MySQL connector/j8?:

These new schemas in the connection URLs enable DNS SRV record support:
jdbc:mysql+srv: For ordinary and basic failover JDBC connections that make use of DNS SRV records.
jdbc:mysql+srv:loadbalance: For load-balancing JDBC connections that make use of DNS SRV records.
jdbc:mysql+srv:replication: For replication JDBC connections that make use of DNS SRV records.
mysqlx+srv: For X DevAPI connections that make use of DNS SRV records.

https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-reference-dns-srv.html

Code

No response

Additional Details

No response

@gaurav517 gaurav517 added the type: question Request for information or clarification. label Feb 20, 2023
@enocom enocom added the priority: p2 Moderately-important priority. Fix may not be included in next release. label Feb 23, 2023
@enocom
Copy link
Member

enocom commented Feb 23, 2023

The Java Connector resolves an instance connection name to a single IP address. Currently, we don't have any support for load balancing across multiple instances.

There's a feature request for that here: #124. If you'd like to add additional information there, please do. We're working on a v2 of the Java Connector and along with other improvements in Cloud SQL, we might be able to revisit this work in the future.

@enocom enocom closed this as completed Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: question Request for information or clarification.
Projects
None yet
Development

No branches or pull requests

3 participants