[
https://issues.apache.org/jira/browse/CURATOR-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568426#comment-17568426
]
Kezhu Wang commented on CURATOR-611:
------------------------------------
Reported before as CURATOR-593. I can't reproduce this in current branch
probably due to ZOOKEEPER-4565.
> EnsembleTracker not appending the chroot node when setting the new connection
> string
> ------------------------------------------------------------------------------------
>
> Key: CURATOR-611
> URL: https://issues.apache.org/jira/browse/CURATOR-611
> Project: Apache Curator
> Issue Type: Bug
> Components: Framework
> Affects Versions: 5.1.0
> Reporter: Francesco
> Priority: Critical
>
> 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.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
