[
https://issues.apache.org/jira/browse/TINKERPOP-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968336#comment-16968336
]
Stephen Mallette commented on TINKERPOP-2289:
---------------------------------------------
Please note that there is discussion on the dev list to revert this change as
it has inadvertently broken existing functionality.
https://lists.apache.org/thread.html/5a606bb428941faaac5c41c4df1526351406ec1ca90574dc9ced7fcd@%3Cdev.tinkerpop.apache.org%3E
Note that the original problem was described here for CosmosDB:
https://groups.google.com/d/msg/gremlin-users/A9rr9jLh5AY/DLguF9QmAQAJ
cc [[email protected]]
> 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.3.9, 3.4.4, 3.5.0
>
>
> 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)
