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

Re-resolve hostnames as fallback when all hosts are unreachable #239

Closed
wprzytula opened this issue Jul 3, 2023 · 1 comment · Fixed by #254
Closed

Re-resolve hostnames as fallback when all hosts are unreachable #239

wprzytula opened this issue Jul 3, 2023 · 1 comment · Fixed by #254
Assignees

Comments

@wprzytula
Copy link

wprzytula commented Jul 3, 2023

If all nodes in the cluster change their IPs at one time, driver can no longer ever contact the cluster; the only solution is to restart the driver. A fallback should be added to the control connection reconnect logic so that when no known host is reachable, all hostnames among initial contact points are reresolved and control connection is attempted to be opened to any of them. If this succeeds, a metadata fetch is issued normally and the whole cluster is discovered with its new IPs.

An analogous feature has been merged to gocql lastly: gocql/gocql#1708

@mykaul mykaul changed the title Reresolve hostnames as fallback when all hosts are unreachable Re-resolve hostnames as fallback when all hosts are unreachable Jul 3, 2023
@avelanarius
Copy link
Member

Rust Driver implementation: scylladb/scylla-rust-driver#770

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants