[
https://issues.apache.org/jira/browse/ZOOKEEPER-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054470#comment-13054470
]
Camille Fournier commented on ZOOKEEPER-781:
--------------------------------------------
[exec] [exec] ./zktest-mt
[exec] [exec] ZooKeeper server startedRunning
...
[exec] [exec] Zookeeper_simpleSystem::testChroot : elapsed 3016 : OK
[exec] [exec] Zookeeper_simpleSystem::testAuth ZooKeeper server
started ZooKeeper server started : elapsed 31369 : OK
Build timed out (after 62 minutes). Marking the build as aborted.
Looks like the mt_c build timed out. Dunno if this is your error, or one of the
bugs in the auth portion of the ZK C client that we recently discovered rearing
its ugly head.
> provide a generalized "connection strategy" for ZooKeeper clients
> -----------------------------------------------------------------
>
> Key: ZOOKEEPER-781
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-781
> Project: ZooKeeper
> Issue Type: New Feature
> Components: c client, java client
> Reporter: Patrick Hunt
> Assignee: Qian Ye
> Fix For: 3.4.0
>
> Attachments: ZOOKEEPER-781.patch, ZOOKEEPER-781.patch,
> ZOOKEEPER-781.patch, ZOOKEEPER-781.patch, ZOOKEEPER-781.patch,
> ZOOKEEPER-781.patch
>
>
> A connection strategy allows control over the way that ZooKeeper clients (we
> would implement this for both c and java apis) connect to a serving ensemble.
> Today we have two strategies, randomized round robin (default) and ordered
> round robin, both of which are hard coded into the client implementation. We
> would generalize this interface and allow users to create their own.
> See this page for more detail:
> http://wiki.apache.org/hadoop/ZooKeeper/ConnectionStrategy
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
