Hi all,
We are setting up a small Hadoop 13 node cluster running 1 HDFS
master, 9 region severs for HBase and 3 map reduce nodes, and are just
installing zookeeper to perform the HBase coordination and to manage a
few simple process locks for other tasks we run.
Could someone please advise what
On Thu, Oct 28, 2010 at 2:52 AM, Tim Robertson
timrobertson...@gmail.com wrote:
We are setting up a small Hadoop 13 node cluster running 1 HDFS
master, 9 region severs for HBase and 3 map reduce nodes, and are just
installing zookeeper to perform the HBase coordination and to manage a
few
Tim, one other thing you might want to be aware of:
http://hadoop.apache.org/zookeeper/docs/current/zookeeperAdmin.html#sc_supervision
Patrick
On Thu, Oct 28, 2010 at 9:11 AM, Patrick Hunt ph...@apache.org wrote:
On Thu, Oct 28, 2010 at 2:52 AM, Tim Robertson
timrobertson...@gmail.com wrote:
I'm trying to debug an issue that maybe you fellas have some ideas for figuring.
In short:
Client 1 updates a znode setting its content to X, then X again, then
Y, and then finally it deletes the znode. Client 1 is watching the
znode and I can see that its getting three nodeDataChanged events
HI everyone,
Is there any situation in which creating a new ZK node with the SEQUENCE
flag should result in a node exists error? I'm seeing this happening
after a failure of a ZK node that appeared to have been the master; when
the new master takes over, my app is unable to create a new
Client 2 is not guaranteed to see X if it doesn't get to asking before the
value has been updated to Y.
On Thu, Oct 28, 2010 at 2:39 PM, Stack st...@duboce.net wrote:
Client 2 is also watching the znode. It gets notified three times:
two nodeDataChanged events(only) and a nodeDeleted event.
On Thu, Oct 28, 2010 at 7:32 PM, Ted Dunning ted.dunn...@gmail.com wrote:
Client 2 is not guaranteed to see X if it doesn't get to asking before the
value has been updated to Y.
Right, but I wouldn't expect the watch to be triggered twice with value Y.
Anyways, I think we have a handle on
On Thu, Oct 28, 2010 at 9:56 PM, Stack st...@duboce.net wrote:
On Thu, Oct 28, 2010 at 7:32 PM, Ted Dunning ted.dunn...@gmail.com
wrote:
Client 2 is not guaranteed to see X if it doesn't get to asking before
the
value has been updated to Y.
Right, but I wouldn't expect the watch to be
