geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-1810) WAN locator exchange doesn't include hostname-for-clients if it is set
Date Tue, 23 Aug 2016 16:39:20 GMT

    [ https://issues.apache.org/jira/browse/GEODE-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433163#comment-15433163
] 

ASF subversion and git services commented on GEODE-1810:
--------------------------------------------------------

Commit 48589a0fa0d841bf53e200dcdc967c82cd95e05b in incubator-geode's branch refs/heads/develop
from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=48589a0 ]

GEODE-1810: WAN locator exchange doesn't include hostname-for-clients if it is set

While exchanging locators, DistributionLocatorID will be constructed
using hostNameforClients. It looks like this was happening if an
embedded locator was started using the start-locator distributed system
property, but not for any other case.

Adding a test that we actually send the hostname for clients to remote
locators.


> WAN locator exchange doesn't include hostname-for-clients if it is set
> ----------------------------------------------------------------------
>
>                 Key: GEODE-1810
>                 URL: https://issues.apache.org/jira/browse/GEODE-1810
>             Project: Geode
>          Issue Type: Bug
>          Components: wan
>            Reporter: Dan Smith
>
> When locator information is exchanged for WAN communication, the hostname-for-clients
value is not included if it is set. Since gateway senders are really just clients, they fail
to connect to the remote locators since they are attempting to connect to an internal address
and not the hostname-for-clients address.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message