ilto:f...@apache.org]
Sent: 21 January 2016 21:09
To: u...@zookeeper.apache.org
Cc: dev@zookeeper.apache.org
Subject: Re: How to handle zookeeper data inconsistency
I should have added that you can use sync() followed by exists() if you want to
catch old deletes that are still propagating. This is su
Hi Mohammad,
A delete operation only needs to reach a quorum to complete and A B form a
quorum in your 3-server ensemble. If the delete operation never gets propagated
to C and other write operations that have been ordered later complete on C,
then you have an issue. If C simply stops
Junqueira [mailto:f...@apache.org]
Sent: 21 January 2016 19:11
To: u...@zookeeper.apache.org
Cc: dev
Subject: Re: How to handle zookeeper data inconsistency
Hi Mohammad,
A delete operation only needs to reach a quorum to complete and A B form a
quorum in your 3-server ensemble. If the delete operation
;
> -Original Message-
> From: Flavio Junqueira [mailto:f...@apache.org]
> Sent: 21 January 2016 19:11
> To: u...@zookeeper.apache.org
> Cc: dev
> Subject: Re: How to handle zookeeper data inconsistency
>
> Hi Mohammad,
>
> A delete operation only needs to reach
elete. However, if the client keeps
> reading, then it should eventually see the delete.
>
> Another thing that is fine is that if no quorum acknowledges a txn, then the
> txn isn't durable.
>
> -Flavio
>
>>
>> -Original Message-
>> From: Flavio Junqueira [mailto:f...@
