May violate the ZAB agreement -- version 3.6.1

version 3.6.1 org.apache.zookeeper.server.quorum.Learner.java line:605 Suppose there is a situation zxid_n is the largest zxid of Participant A (the leader has just resumed from downtime). Zxid_n has not been recognized by the quorum. Assuming Participant A is elected as the Leader, then if a fol

Re: Preparing for 3.6.2 release ?

Sorry for late reply @Mate ZOOKEEPER-3905 is in. I am running a few smoke tests on branch-3.6, I have also cleaned up JIRA There is only this task about updating the CI reference in pom.xml https://issues.apache.org/jira/browse/ZOOKEEPER-3801 Christopher alredy sent a PR, but now Jenkins link cha

C client build is failing for branch-3.5 on new CI

Hi ZooKeepers, I am checking the new CI system and I noticed this error for branch-3.5 on the C client build, the error does not occur on branch-3.6 and on master TestClient.o `test -f 'tests/TestClient.cc' || echo '/home/jenkins/jenkins-home/workspace/er-multi-branch-build_branch-3.5/zookeeper-cl

Re: May violate the ZAB agreement -- version 3.6.1

How is it that participant A would have a later zxid than the leader? In particular, it seems to me that it should be impossible to have these two facts be true: 1) a transaction has been committed with zxid = z_0. This implies that a quorum of the cluster has accepted this transaction and it has

Sequential Consistency Guarantees

Hello! We were investigating an issue with consistent reads in ZK which made us question our assumptions. We believe that ZK offers sequential consistency such that if a client creates a node with zxid 0x11122a, it should be able to see (read) all data changes at least up to that zxid. Could

Re: Sequential Consistency Guarantees

I think that the answer depends a bit on what you mean by "client". If you mean client connection (as in the result of opening a connection to a Zookeeper cluster), then you should see things in order so that reads following a successful and acknowledged commit should see only states at or after th

Re: Sequential Consistency Guarantees

Can you describe your evidence in more detail as you understand it? On Thu, Aug 27, 2020 at 10:26 AM Stanislav Kozlovski wrote: > Hello! > > We were investigating an issue with consistent reads in ZK which made us > question our assumptions. > We believe that ZK offers sequential consistency s

[jira] [Created] (ZOOKEEPER-3922) Add support for two server ZooKeeper with hardware oracle

Benjamin Reed created ZOOKEEPER-3922: Summary: Add support for two server ZooKeeper with hardware oracle Key: ZOOKEEPER-3922 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3922 Project: ZooKe

Re: Re: Sequential Consistency Guarantees

---> if a client creates a node with zxid 0x11122a, it should be able to see (read) all data changes at least up to that zxid. You may have a misunderstanding on what sequential consistency guarantees. For your example: Suppose that you have following operations: create /mypath v0 (0x11000

Re: C client build is failing for branch-3.5 on new CI

Thanks for raising the issue! I checked the logs. The 'configure' step finds the openSSL library before make: 19:58:34 checking openssl/ssl.h usability... yes 19:58:34 checking openssl/ssl.h presence... yes 19:58:34 checking for openssl/ssl.h... yes 19:58:34 checking for SSL_CTX_new in -lssl..

Re: Re: May violate the ZAB agreement -- version 3.6.1

@李珣The situation you describe may have conceptual deviations about how the consensus protocol works:---> Since the data of the follower when the follower uses the DIFF method to synchronize with the leader is still in the memory, it has not had time to persist1. The write path is: write transact