[KUDU-2415] READ_YOUR_WRITES scan with no prior operation fails

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.0
• Fix Version/s: 1.8.0
• Component/s: client, tserver
• Target Version/s: 1.8.0
• Assignee: Andrew Wong
• Reporter: Todd Lipcon
• Created: 24/Apr/18 22:21
• Updated: 18/Dec/18 05:26
• Resolved: 18/Dec/18 05:26

Description

If I create a new Java client, and then perform a scan in READ_YOUR_WRITES mode without having done any prior operations from that client, it sends an RPC with read_mode=READ_YOUR_WRITES but without any propagated or snapshot timestamp field set. The server seems to interpret this as a value '0' and then fails with the error:

Snapshot timestamp is earlier than the ancient history mark. Consider increasing the value of the configuration parameter --tablet_history_max_age_sec. Snapshot timestamp: P: 0 usec, L: 1 Ancient History Mark: P: 1524607330402072 usec, L: 0 Physical time difference: -1524607330.402s

Issue Links

• relates to: KUDU-2473 READ_YOUR_WRITES error on snapshot timestamp
• relates to: KUDU-2233 Check failure during compactions: pv_delete_redo != nullptr