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

Fix: Only using a single resolved IP when connecting with hostname #488

Merged
merged 1 commit into from
Nov 13, 2020

Conversation

mpenick
Copy link
Contributor

@mpenick mpenick commented Oct 28, 2020

SocketConnector::resolved_address_offset_ is never incremented because
the first parameter was wrong. Also, this adds a default filter for
resolver hints to prevent duplicates in the resolved IPs.

`SocketConnector::resolved_address_offset_` is never incremented because
the first parameter was wrong. Also, this adds a default filter to for
resolver hints to prevent duplicates in the resolved IPs.
@mpenick mpenick merged commit e0be47f into master Nov 13, 2020
simonebaracchi pushed a commit to cloudian/cpp-driver that referenced this pull request Jan 28, 2021
…atastax#488)

`SocketConnector::resolved_address_offset_` is never incremented because
the first parameter was wrong. Also, this adds a default filter to for
resolver hints to prevent duplicates in the resolved IPs.
@mpenick mpenick deleted the fix_ip_load_balancing branch March 1, 2021 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant