[ 
https://issues.apache.org/jira/browse/KUDU-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Alves resolved KUDU-398.
------------------------------
       Resolution: Fixed
    Fix Version/s: Public beta

> 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
>             Fix For: Public beta
>
>
> 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)

Reply via email to