[
https://issues.apache.org/jira/browse/KUDU-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576295#comment-15576295
]
David Alves commented on KUDU-398:
----------------------------------
Oh this was merged. Created KUDU-1703 to track handling the arbitrary waiting
post-clock update that you mentioned in the gerrit.
> Snapshot scans should only refuse scans with timestamps whose value is >
> now+error
> ----------------------------------------------------------------------------------
>
> Key: KUDU-398
> URL: https://issues.apache.org/jira/browse/KUDU-398
> Project: Kudu
> Issue Type: Sub-task
> Components: tserver
> Affects Versions: M4
> Reporter: David Alves
> Assignee: Todd Lipcon
> Priority: Minor
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
