[KUDU-1704] Add a new read mode to perform bounded staleness snapshot reads

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0
• Fix Version/s: 1.7.0
• Component/s: client
• Labels: consistency
• Assignee: Hao Hao
• Reporter: David Alves
• Created: 14/Oct/16 19:26
• Updated: 16/Jun/19 17:51
• Resolved: 14/Mar/18 23:26

Description

It would be useful to be able to perform snapshot reads at a timestamp that is higher than client's previous writes (achieve read-your-writes), thus improving recency, but lower that the server's oldest inflight transaction, thus minimizing the scan's chance to block.

Such a mode would not guarantee linearizability, but would still allow for client-local read-your-writes, which seems to be one of the properties users care about the most.

The detail design of the mode is available in the linked design doc.

This should likely be the new default read mode for scanners.

Issue Links

• is duplicated by: KUDU-1498 Add support to Java client for read-your-writes consistency
• is duplicated by: KUDU-1499 Add friendly C++ API for read-your-writes consistency
• is related to: KUDU-2352 Add an API to allow bounded staleness scan
• is related to: KUDU-2333 Add a RYW/RYR test to jepsen
• relates to: KUDU-1189 On reads at a snapshot that touch multiple tablets, without the user setting a timestamp, use the timestamp from the first server for following scans
• relates to: KUDU-1368 Setting snapshot timestamp to last propagated timestamp should include prior writes
• relates to: KUDU-1454 Spark and MR jobs running without scan locality
• relates to: KUDU-1497 Full support for read-your-writes consistency
• relates to: KUDU-1869 Scans do not work with hybrid time disabled and snapshot reads enabled
• links to: Design Doc