We have a few entries in the FAQ about this: <a href="http:&#x2F;&#x2F;getkudu.io&#x2F;faq.html#what-is-kudus-consistency-model-is-kudu-a-cp-or-ap-system" rel="nofollow">http:&#x2F;&#x2F;getkudu.io&#x2F;faq.html#what-is-kudus-consistency-model-i...</a>
as well as some more in-depth docs: <a href="http:&#x2F;&#x2F;getkudu.io&#x2F;docs&#x2F;transaction_semantics.html" rel="nofollow">http:&#x2F;&#x2F;getkudu.io&#x2F;docs&#x2F;transaction_semantics.html</a><p>Basically the short answer, though, is that reads are not done by quorum, but the client can specify if they need &quot;up to date&quot; reads. If they do, currently, we force reads to go to the leader, but have a roadmap for how to read from other replicas (see the Spanner paper for a rough idea how that can work).