[
https://issues.apache.org/jira/browse/KUDU-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451395#comment-16451395
]
Todd Lipcon edited comment on KUDU-2415 at 4/24/18 11:26 PM:
-------------------------------------------------------------
One other detail that looks important: this only happens if the tablet has
never been written to. In that case the MvccManager has state like:
{code}
{cur_snap_=MvccSnapshot[committed={T|T < 1}], in_flight=0, safe=0,
earliest=18446744073709551615}
{code}
and so the clean time is getting set to 0. This is as of commit
c4b8804ac16ebfe373efa33f82d86a0e3d677e72
was (Author: tlipcon):
One other detail that looks important: this only happens if the tablet has
never been written to. In that case the MvccManager has state like:
{cur_snap_=MvccSnapshot[committed={T|T < 1}], in_flight=0, safe=0,
earliest=18446744073709551615}
and so the clean time is getting set to 0. This is as of commit
c4b8804ac16ebfe373efa33f82d86a0e3d677e72
> 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
> Priority: Major
>
> 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)
