[CURATOR-664] EnsembleTracker use resolved server address in connection string if client address is wildcard

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.4.0
• Fix Version/s: 5.5.0
• Component/s: Framework
• Assignee: Kezhu Wang
• Reporter: Kezhu Wang
• Created: 29/Mar/23 01:29
• Updated: 02/Apr/23 06:58
• Resolved: 31/Mar/23 11:59

Description

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.

Issue Links

• relates to: CURATOR-638 Curator disconnect from zookeeper when IPs change
• supercedes: CURATOR-384 EnsembleTacker.configToConnectionString can render connection impossible
• links to: GitHub Pull Request #452