+1
I put it up on a cluster under hbase and ran loads against it over
last few hours. Nothing untoward in logs. Played around w/ zkcli.
It seems to behaving same as 3.3.1.
St.Ack
On Wed, Nov 10, 2010 at 3:24 PM, Henry Robinson he...@cloudera.com wrote:
+1
Python looks good.
On 10
+1
I installed it under hbase cluster as a 5-node ensemble. Looks like
it works like 3.3.0. Did some messing sending nc commands. No prob.
St.Ack
On Thu, May 13, 2010 at 4:52 PM, Mahadev Konar maha...@yahoo-inc.com wrote:
+1.
Ran ant tests and some manual testing to bring up a cluster and
current
practices. We also need to include this information in our release notes.
http://wiki.apache.org/hadoop/ZooKeeper/Roadmap
https://issues.apache.org/jira/browse/ZOOKEEPER-727
Stack, in your specific case you are seeing that 3.3 client works fine with
3.2 server. In 3.3 we added a new
+1
Put it under hbase and ran a loading on a small cluster. Completed.
Checked out doc. Looks right on cursory glance.
St.Ack
On Tue, Dec 8, 2009 at 2:32 PM, Patrick Hunt ph...@apache.org wrote:
I've created a second candidate build for ZooKeeper 3.2.2. This is a bug
fix release
+1 Ran it in place of zk-3.2.1 in hbase context for an upload and nothing
untoward examining logs. Took a quick gander at the doc. and nothing
obviously amiss.
St.Ack
On Mon, Nov 23, 2009 at 4:53 PM, Patrick Hunt ph...@apache.org wrote:
Hadoop PMC,
Please test and vote on this release in
: Improvement
Reporter: stack
I'd like to ask a running quorum what its configuration is. I'd want to know
stuff like session timeout and tick times.
Use case is that in hbase there is no zoo.cfg usually; the configuration is
manufactured and piped to the starting zk server. I want to know
[
https://issues.apache.org/jira/browse/ZOOKEEPER-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781074#action_12781074
]
stack commented on ZOOKEEPER-587:
-
If server changes the timeout on the client, yeah