[jira] [Closed] (TINKERPOP-2289) Use address instead of hostname for connection

2019-10-04 Thread Stephen Mallette (Jira)


 [ 
https://issues.apache.org/jira/browse/TINKERPOP-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Mallette closed TINKERPOP-2289.
---
Resolution: Fixed

> 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)


[jira] [Closed] (TINKERPOP-2289) Use address instead of hostname for connection

2019-09-03 Thread stephen mallette (Jira)


 [ 
https://issues.apache.org/jira/browse/TINKERPOP-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette closed TINKERPOP-2289.
---
Fix Version/s: 3.4.4
   3.3.9
   3.5.0
 Assignee: stephen mallette
   Resolution: Done

> 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.2#803003)