Yeah, that's what I thought too. When I said "locked" I meant ZK ensembly will block access (read and write) to the clients that are connecting to the parent node. Say you and I both connecting to "/example/doug". I issue a write to create "/example/doug/lock". Then ZK will block you from accessing the "/example/doug" and anything below that. But if Henry's client is connecting to "/anotherexample" and Henry tries to read a node there he will not be blocked. I'll buy Henry's answer. Thanks
-- View this message in context: http://zookeeper-user.578899.n2.nabble.com/Does-Zookeeper-Lock-Entire-Znode-Tree-During-a-Write-tp7558524p7560793.html Sent from the zookeeper-user mailing list archive at Nabble.com.
