You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Andrew Wong (JIRA)" <ji...@apache.org> on 2018/12/18 05:27:00 UTC
[jira] [Closed] (KUDU-2415) READ_YOUR_WRITES scan with no prior
operation fails
[ https://issues.apache.org/jira/browse/KUDU-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wong closed KUDU-2415.
-----------------------------
Resolution: Fixed
Assignee: Andrew Wong (was: Hao Hao)
Fix Version/s: 1.8.0
This should be fixed per the patches done for KUDU-2463. We're now guaranteed to have a non-0 clean time when servicing a scan.
> READ_YOUR_WRITES scan with no prior operation fails
> ---------------------------------------------------
>
> Key: KUDU-2415
> URL: https://issues.apache.org/jira/browse/KUDU-2415
> Project: Kudu
> Issue Type: Bug
> Components: client, tserver
> Affects Versions: 1.7.0
> Reporter: Todd Lipcon
> Assignee: Andrew Wong
> Priority: Major
> Fix For: 1.8.0
>
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)