[
https://issues.apache.org/jira/browse/TINKERPOP-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943716#comment-16943716
]
Stephen Mallette commented on TINKERPOP-2289:
---------------------------------------------
any thoughts on what the solution is here? I decided to just try to deal with
the "localhost" aspect of this as i'm not sure what else we might do. You can
see the change in this PR:
https://github.com/apache/tinkerpop/pull/1206
does that solve things? better way? i'm not so good with all this networking
stuff so there might be nicer ways to deal with this problem but we need
something sooner than later because we go to code freeze next week for release.
Happy to hear any feedback on this one...thanks.
> Use address instead of hostname for connection
> ----------------------------------------------
>
> Key: TINKERPOP-2289
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2289
> Project: TinkerPop
> Issue Type: Bug
> Components: driver
> Affects Versions: 3.4.3
> Reporter: Hua Jiang
> Assignee: Stephen Mallette
> Priority: Minor
> Fix For: 3.5.0, 3.3.9, 3.4.4
>
>
> The current implementation uses hostname to create connections. It causes two
> problems in a scenario where multiple addresses are bound to the same domain
> name.
> # Load balancing is broken because multiple `Host` may connect to the same
> address, and some addresses may have no connection at all.
> # It produces misleading log messages because the address in the host label
> may not be the one the host is actually connected to.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
