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.

Sign up for GitHub

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

Jump to bottom

Bug: Can't detect useHostColumn when connecting with hostname rather than IP #16

Open
1 of 2 tasks
FranckPachot opened this issue Jan 4, 2022 · 1 comment
Open
1 of 2 tasks

Bug: Can't detect useHostColumn when connecting with hostname rather than IP #16

FranckPachot opened this issue Jan 4, 2022 · 1 comment
Assignees
@kneeraj

Comments

@FranckPachot
Copy link

FranckPachot commented Jan 4, 2022 •
edited by Sfurti-yb
Loading

  • bug report
  • feature request

When we connect with hostname rather than IP addess we get: WARNING: TopologyAwareLoadBalancer: Either private or public should have matched with one of the servers
This is caused by getCurrentServers comparing the host in the url (hostConnectedTo with the IP in yb_servers()

Driver Version: 42.3.0
@kneeraj kneeraj self-assigned this Jan 5, 2022
@Sfurti-yb Sfurti-yb mentioned this issue Feb 8, 2022
Merged
@ashetkar
Copy link

ashetkar commented Mar 2, 2022

The fix will be available in 42.3.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kneeraj kneeraj

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kneeraj @ashetkar @FranckPachot