Interesting, that basically means if I want strict order, I have to
use the async api?
~~~
Hadoop training and consulting
http://www.scaleunlimited.com
http://www.101tec.com
On Aug 3, 2009, at 8:10 PM, Benjamin Reed wrote:
I assume you are calling the synchronous
I assume you are calling the synchronous version of exists. The callbacks for
both the watches and async calls are processed by a callback thread, so the
ordering is strict. Synchronous call responses are not queued to the callback
thread. (this allows you to make synchronous calls in callbacks
Hi,
I'm running into following problem writing a fasade for Zk Client (http://github.com/joa23/zkclient/
)
1.) Subscribe a watch via exist(path, true) for a path.
2.) Create a persistent node.
3.) Call exist and it returns true
4.) Zookeeper sends a NodeCreated event.
I would expect that the
That'd be perfect. Thanks!
> -Original Message-
> From: Mahadev Konar [mailto:maha...@yahoo-inc.com]
> Sent: Monday, August 03, 2009 4:24 PM
> To: zookeeper-user@hadoop.apache.org
> Subject: Re: Unending Leader Elections in WAN deploy
>
> Hi Todd,
> Most of the patches that you mention
Hi Todd,
Most of the patches that you mention should be in the branch 3.2 by tomm
or so. 481, 479 are already in. 480 and 491 should be in by tomm. Would that
suffice for you?
Thanks
mahadev
On 8/3/09 4:21 PM, "Todd Greenwood" wrote:
> Another problem...I've reverted to the latest versions
Hi all,
A quick reminder that Scale Unlimited will run a 2 day Hadoop BootCamp
in Berlin on August 27th and 28th.
This 2 day course is for managers and developers who want to quickly
become experienced with Hadoop and related technologies.
The BootCamp provides training in MapReduce Theo
Another problem...I've reverted to the latest versions of the patches
that are not specific to branch-3.2, and I'm getting two compilation
errors:
build-generated:
[javac] Compiling 44 source files to
/home/toddg/asi/workspaces/main/Main/RSI/etc/holmes/main/zookeeper/src/p
atched/branch-3.2/bu
Flavio,
I notice that you've updated the patches referenced for the WAN
deployment. There appears to be an order dependency w/ respect to these
four patches...
ZOOKEEPER-473.patch ZOOKEEPER-479-branch3.2.patch
ZOOKEEPER-481-branch3.2.patch ZOOKEEPER-491.patch
473 -> 479 (479 fails)
to...@toddg
Please do enter a JIRA. Looking at the source it seems that we log and
error, but the calling code continues. I think this is happening because
the chroot c lib code is not handling znode watches separate from state
change notifications.
The calling code just continues after logging an (invali
