Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Zookeeper >> mail # user >> sometimes I can't read data I just wrote..race condition or misunderstanding?


Copy link to this message
-
sometimes I can't read data I just wrote..race condition or misunderstanding?
We're running a five node cluster in AWS and sometimes if I do a read
immediately after doing a write ZK does not find the data I just wrote.

I may just have a flawed model but is this a case of "writes go to the
master, while reads can go to any node in the cluster?".  We are thinking
that perhaps our write went to the master and then our read went to a
follower that hadn't gotten the write yet?

Along the same lines...when does a watch fire?  After the leader has the
change or after all followers have gotten the change?

Any insights would be appreciated, thanks.

Brian
http://about.me/BrianTarbox

 
+
Raúl Gutiérrez Segalés 2014-03-04, 20:23
+
Camille Fournier 2014-03-04, 20:26
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB