It could be because your client has not connected properly to a ZooKeeper
server. Have you taken a look at the logs on the server side to make sure that
a session has been created? Could you give me a little more detail about your
setup?
-Flavio
- Original Message
From: Avinash Laks
When I do execute the folloiwing code :
String pathCreated = zk.create(createPath, new byte[0], Ids.OPEN_ACL_UNSAFE,
(CreateFlags.SEQUENCE | CreateFlags.EPHEMERAL) );
It seems to fail silently w/o reporting any errors. I mean I have a log
statement after this line which never shows up. However
These are sequence of interactions with ZooKeeper:
(1) Instantiate Zookeeper and perform the checks for a bunch of znodes. All
this works as expected.
(2) Spawn a thread which tries to perform leader election. This is where I
am trying to create the znode with the sequence numbers.
I am assuming
Hi Avinash,
Can you post sample code to explain what you are doing? Its harder to see
from what you explained as to why zookeeper should fail.
As for session timeout, it means that your session will be expired after 5000ms
if your zookeeper client goes away.
Mahadev
___
Hello,
I was wondering whether ZooKeeper includes Paxos in its code. Can you tell
me which part of the code is about the Paxos? Maybe ZooKeeper may provide a
good chance for people to see how to implement Paxos correctly and
efficiently.
Thank you.
-
I am not sure that the full Paxos algorithm is applicable to zookeeper.
Much more important internally is the ability to nominate a single cluster
leader which is simpler than Paxos. Once there is a cluster leader, then
all updates go through that single host which, in turn, makes any client
based
No. Internally we use an atomic broadcast protocol (which is what Paxos
would provide us) to keep the replicas in sync, but the protocol is much
simpler than Paxos. We take advantage the fact that we use FIFO channels
(TCP) and always use a leader along with some operational rules which
results in
On Jun 6, 2008, at 17:42 , Benjamin Reed wrote:
> No. Internally we use an atomic broadcast protocol (which is what
> Paxos would provide us) to keep the replicas in sync, but the
> protocol is much simpler than Paxos.
Fundamentally, I am assuming that the protocol you use must look
similar
Actually it was my bad. I figured out what I was doing incorrectly. All is
good.
Thanks
Avinash
On Fri, Jun 6, 2008 at 1:59 PM, Benjamin Reed <[EMAIL PROTECTED]> wrote:
> Are you sure there are no exceptions being thrown? So after the create the
> path is not there? Is it possible the create is
On Jun 6, 2008, at 17:42 , Benjamin Reed wrote:
> No. Internally we use an atomic broadcast protocol (which is what
> Paxos would provide us) to keep the replicas in sync, but the
> protocol is much simpler than Paxos.
After reading QuorumPeer, I think it is safe to say that Zookeeper
implem
There are some basic elements that all atomic broadcast protocols have, but I
don't think that makes them all the same.
There actually are two parts to the atomic broadcast protocol. The
establishment of the leader, and the leading phase.
A big difference between us and Paxos is that we never d
11 matches
Mail list logo
