[
https://issues.apache.org/jira/browse/GEODE-9634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17427742#comment-17427742
]
ASF GitHub Bot commented on GEODE-9634:
---------------------------------------
pdxcodemonkey merged pull request #872:
URL: https://github.com/apache/geode-native/pull/872
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Wan replication between clusters on localhost broken by change to IP lookup
> ---------------------------------------------------------------------------
>
> Key: GEODE-9634
> URL: https://issues.apache.org/jira/browse/GEODE-9634
> Project: Geode
> Issue Type: Bug
> Components: wan
> Affects Versions: 1.15.0
> Reporter: Blake Bender
> Priority: Blocker
>
> This was the fix for GEODE-8955 (PR #6045). Here's a description from the
> start of the Slack discussion thread:
> "PR 6045 made on geode-wan LocatorHelper class seems to have broken WAN
> replication between two clusters on localhost. I get the ridiculous nature of
> WAN over localhost. Is it intentional that localhost is replaced with a local
> interface IP by the changes made in the PR? The result is a test in the
> geode-native pipeline does not work anymore since one site can’t see the
> other since the locators are bound to localhost but trying to connection to
> each other on a non-localhost IP address. Did we run into this same issue on
> any of our Java based tests?"
> Need to determine if this is desired behavior or not. If not, the old
> behavior should be restored. If so, geode native team needs a JIRA ticket to
> fix their Wan integration test(s) in CI, where this issue was detected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
