You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Enrico Olivelli (Jira)" <ji...@apache.org> on 2023/03/31 12:00:00 UTC
[jira] [Resolved] (CURATOR-664) EnsembleTracker use resolved server address in connection string if client address is wildcard
[ https://issues.apache.org/jira/browse/CURATOR-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Enrico Olivelli resolved CURATOR-664.
-------------------------------------
Resolution: Fixed
> EnsembleTracker use resolved server address in connection string if client address is wildcard
> ----------------------------------------------------------------------------------------------
>
> Key: CURATOR-664
> URL: https://issues.apache.org/jira/browse/CURATOR-664
> Project: Apache Curator
> Issue Type: Bug
> Components: Framework
> Affects Versions: 5.4.0
> Reporter: Kezhu Wang
> Priority: Major
> Fix For: 5.5.0
>
>
> In construction of connection string, {{EnsembleTracker}} resorts to server address if client address is wildcard. In case where server address is DNS name, it should use that but not a resolved ip address. Otherwise, if server is migrated to another machine, it becomes unreachable through ip address in connection string.
> CURATOR-638 probably cover this, but https://github.com/apache/curator/pull/425 did not resolve this case. Create a new issue to keep its "Fix Version" unchanged.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)