ivandika3 commented on PR #1362: URL: https://github.com/apache/ratis/pull/1362#issuecomment-4030318508
Thanks @szetszwo for the clarification, apologies for the late reply. Using appliedIndex might not preserve monotonicity since follower might apply faster than the leader (or other follower). > Change Leader to send appliedIndex (or repliedIndex depending on the readIndex conf) as [leaderCommit](https://github.com/apache/ratis/blob/a5651f6e9a95f5b5ac44ff01363b7de1c8b4c026/ratis-proto/src/main/proto/Raft.proto#L185) in appendEntries. Then, the following invariants will hold: Let me attempt this first. > Add a seenIndex to the read requests. The server (leader or follower) will wait until max(seenIndex, readIndex) is applied. Does this mean that the client needs to keep track of this seenIndex across multiple requests? The idea seems to be similar to readAfterWriteConsistentIndex. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
