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 Threaded View
Zookeeper >> mail # user >> Consistency in zookeeper


Copy link to this message
-
Re: Consistency in zookeeper
Even if you do the sync, another client can make a change before you do the subsequent read.

-JZ

On Mar 1, 2013, at 1:50 PM, Martin Kou <[EMAIL PROTECTED]> wrote:

> Yasin,
>
> If the two clients are connected to two different ZooKeeper servers in the
> cluster, then, yes.
>
> Generally, if you're worried that there may be another client working on
> the same key path, then you should sync() before reading.
>
> Best Regards,
> Martin Kou
>
> On Fri, Mar 1, 2013 at 1:38 PM, Yasin <[EMAIL PROTECTED]> wrote:
>
>> So, if the read request is made by some other client, it will not get the
>> updated value without sync, right?
>>
>>
>>
>> --
>> View this message in context:
>> http://zookeeper-user.578899.n2.nabble.com/Consistency-in-zookeeper-tp7578531p7578542.html
>> Sent from the zookeeper-user mailing list archive at Nabble.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