[CURATOR-578] EnsembleTracker replace hostname connectString with wrong ip from zk config

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.1
• Fix Version/s: 5.4.0
• Component/s: Client
• Assignee: Unassigned
• Reporter: ying.li
• Created: 16/Jul/20 12:12
• Updated: 17/Jul/22 08:04
• Resolved: 17/Jul/22 08:04

Description

I have a zookeeper cluster  which run on a k8s cluster. and I use host name to  connect the zookeeper(like : zookeeper-0.zookeeper-headless.default.svc.cluster.local:2181,zookeeper-1.zookeeper-headless.default.svc.cluster.local:2181,zookeeper-2.zookeeper-headless.default.svc.cluster.local:2181).

 

When the zookeeper restart. the zk pod's ip will change.  then  I find my client will use the IP to recreate a client without using the hostname . but the IP is not the latest IP from hostname.so, it will make client never connect to zk , unless restart the client

 

After some debug ,I find the EnsembleTracker will change the connectString from hostname to ip when receive the congfig change  event. But in many case, the IP get from hostname will not change after  zk  restart in k8s. so, it will make client never connect to zk , unless restart the client

 

Issue Links

• duplicates: CURATOR-638 Curator disconnect from zookeeper when IPs change