Re: May violate the ZAB agreement -- version 3.6.1

Hi hanm Thanks This is the issue in jira https://issues.apache.org/jira/browse/ZOOKEEPER-3911 ——— Below are my thoughts Before the server becomes the real leader, the follower needs

Re: May violate the ZAB agreement -- version 3.6.1

Hi Xun, I think this is a bug, your test case is sound to me. Do you mind creating a JIRA for this issue? Followers should not ACK NEWLEADER without ACK every transaction from the DIFF sync. To ACK every transaction, a follower either persists the transaction in log, or takes a snapshot before

[jira] [Created] (ZOOKEEPER-3923) Leader election issues with Istio

Matteo Merli created ZOOKEEPER-3923: --- Summary: Leader election issues with Istio Key: ZOOKEEPER-3923 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3923 Project: ZooKeeper Issue

Re: May violate the ZAB agreement -- version 3.6.1

There is a example in the link, would you understand what I mean？ https://drive.google.com/file/d/1jy3kkVQTDYGb4iV1RaPMBbEWLZZltTQG/view?usp=sharing Since version 3.4, the quorum of followers and the leader did not synchronize the files immediately when the synchronization was completed, and

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

Il Ven 28 Ago 2020, 08:20 Szalay-Bekő Máté ha scritto: > 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

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

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

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