Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
Zookeeper, mail # user - Consistency in zookeeper


+
Yasin 2013-02-28, 23:35
+
Alexander Shraer 2013-02-28, 23:49
+
Rakesh R 2013-03-01, 05:32
+
kishore g 2013-03-01, 17:49
+
Alexander Shraer 2013-03-01, 18:19
+
Flavio Junqueira 2013-03-01, 20:35
+
Yasin 2013-03-01, 20:50
+
Yasin 2013-03-01, 20:50
+
kishore g 2013-03-01, 21:17
+
Yasin 2013-03-01, 21:38
+
Martin Kou 2013-03-01, 21:50
+
Jordan Zimmerman 2013-03-01, 22:01
Copy link to this message
-
Re: Consistency in zookeeper
Ted Dunning 2013-03-02, 02:03
Yes.  Sync doesn't guarantee up to date.  It guarantees an ordering.  It
guarantees that if event A involves a ZK update and if you can guarantee
that A occurs before sync, then any read on a client C that is done after a
sync on C will see a successor state of A.

On Fri, Mar 1, 2013 at 2:01 PM, Jordan Zimmerman <[EMAIL PROTECTED]
> wrote:

> 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.
> >>
>
>
+
Rakesh R 2013-03-03, 09:51
+
Ted Dunning 2013-03-02, 02:00