[
https://issues.apache.org/jira/browse/ZOOKEEPER-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964813#action_12964813
]
Camille Fournier commented on ZOOKEEPER-836:
--------------------------------------------
I am not a fan of the StaticHostProvider changing the random round robin
behavior of the current setup. In the case of a poorly-behaving ZK server that
allows connections briefly and then terminates them, the client is trapped by
this server if it happens to be at the start of its randomized list. Is it
likely to happen? Probably not, but I don't see any compelling reason to
introduce this possible problem.
> hostlist as string
> ------------------
>
> Key: ZOOKEEPER-836
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-836
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: java client
> Affects Versions: 3.3.1
> Reporter: Patrick Datko
> Assignee: Thomas Koch
> Attachments: ZOOKEEPER-836.patch, ZOOKEEPER-836.patch,
> ZOOKEEPER-836_2.patch
>
>
> The hostlist is parsed in the ctor of ClientCnxn. This violates the rule of
> not doing (too much) work in a ctor. Instead the ClientCnxn should receive an
> object of class "HostSet". HostSet could then be instantiated e.g. with a
> comma separated string.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
