[CURATOR-611] EnsembleTracker not appending the chroot node when setting the new connection string

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 5.1.0
• Fix Version/s: 5.6.0
• Component/s: Framework
• Assignee: Kezhu Wang
• Reporter: Leonissimo
• Created: 18/Aug/21 11:48
• Updated: 05/May/23 07:56
• Resolved: 05/May/23 07:56

Description

The EnsembleTracker does not add the chroot node when setting the connection string upon receiving a new configuration event.

The new connection string is created by the method  EnsembleTracker.configToConnectionString(QuorumVerifier data) as a comma separated list of <ip:port> for each zookeeper server in the QuorumVerfier, but
the chroot node is not appended to the newly created connection string. 

So for example if the initial connection string is 

zookeeper01:2080,zookeeper02:2080/config/prop

when zookeeper03 joins the cluster, the client connection string is set to

171.19.10.23.2080,171.19.10.24.2080,171.19.10.25.2080

and "/config/prop" gets stripped out.

The problem manifests itself upon a re-connection to zookeeper, because the client will point to the wrong paths.

 

 

 

Issue Links

• duplicates: CURATOR-593 EnsembleTracker "configToConnectionString" method doesn't include zookeeper chroot
• is blocked by: ZOOKEEPER-4565 Config watch path get truncated abnormally and fail chroot zookeeper client