Details
-
Sub-task
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
M4
-
None
Description
We currently reject a snapshot scan timestamp if it's value if beyond clock->Now(). We should only reject it if it's value is beyond clock->Now() + error, since all values < clock->Now() + error can still be generated by perfectly valid servers.
We should wait for the timestamp to be safe in all cases.
Marking this as best effort as this does not make kudu return wrong values, it just makes it a little less tolerant to skew than it could be.
Attachments
Issue Links
- relates to
-
KUDU-1012 ksck says "snapshot time in the future" on busy table
- Resolved