Thanks, yes that helps. Few more questions around read/write semantics:
1. Writes are acknowledged to the client when committed to majority? 2. Are reads via the query method strongly consistent? Do they get routed to the leader transparently? Regards, Asad ________________________________ From: Tsz Wo Sze <[email protected]> Sent: Wednesday, November 17, 2021, 7:18 p.m. To: [email protected] Subject: Re: Replication factor Hi Asad, Yes, you are right. Replication factor is the same as the number of members (servers) in a Raft group since each member has a copy of the states. To change the replication factor, change the number of the members. Hope it helps. Tsz-Wo On Thu, Nov 18, 2021 at 5:49 AM Asad Awadia <[email protected]<mailto:[email protected]>> wrote: Apache Ratis - In Search of a Usable Raft Library<https://www.slideshare.net/TszWoNicholasSze/apache-ratis-in-search-of-a-usable-raft-library> slide 9/23 it talks about membership changes and replication factor. How is the replication factor configured? I don't see any functions or mention of that? Only on the watch rpc. Is replication factor how many servers should keep a copy of the data? Is my understanding correct? Or is this something completely different? Thank you for all the work! I am really looking forward to using this project. Regards, Asad
