szetszwo commented on PR #5288: URL: https://github.com/apache/ozone/pull/5288#issuecomment-1720112411
> ... should probably be off by default until is sees more testing. @sodonnel , thanks for taking a look! Sure, let's disable it by default. > Is it possible for some followers to fall behind - if so how is this handled? > > Or are the followers always totally up to date? Eg, is a commit key on the leader absolutely available on all followers when the client call to commit the key returns, so that if a client immediately issues a read and it hits a different OM, it will see the data? In short, the read-index algorithm handle it. For more details, see the design doc in [RATIS-1557](https://issues.apache.org/jira/browse/RATIS-1557) and also the [Raft thesis, Section 6.4](https://web.stanford.edu/~ouster/cgi-bin/papers/OngaroPhD.pdf) > Is there a performance implication for writes by setting this on? Eg in the old way, as the followers slightly behind as they apply the Ratis log, while with this on its more like a 3 way commit for each write, so a delay (eg GC pause) on one OM would affect the write time on the leader? The writes are the same. The feature only change the behavior for read. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
