You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Thomas Tauber-Marshall (JIRA)" <ji...@apache.org> on 2018/06/14 16:24:00 UTC
[jira] [Resolved] (KUDU-2473) READ_YOUR_WRITES error on snapshot
timestamp
[ https://issues.apache.org/jira/browse/KUDU-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Tauber-Marshall resolved KUDU-2473.
------------------------------------------
Resolution: Duplicate
Fix Version/s: n/a
dup of KUDU-2415
> READ_YOUR_WRITES error on snapshot timestamp
> --------------------------------------------
>
> Key: KUDU-2473
> URL: https://issues.apache.org/jira/browse/KUDU-2473
> Project: Kudu
> Issue Type: Bug
> Components: impala
> Reporter: Thomas Tauber-Marshall
> Priority: Critical
> Fix For: n/a
>
>
> I'm trying to implement support for READ_YOUR_WRITES for Impala, but I'm finding that if SetLatestObservedTimestamp() isn't called (eg. because we haven't interacted with Kudu yet in the current session and don't have a timestamp to set), attempting to scan tables always fails with an error of the form:
> org.apache.kudu.client.NonRecoverableException: 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: 1528845756599966 usec, L: 0 Physical time difference: -1528845756.600s
> Minimal repro:
> {noformat}
> KuduClientBuilder b = new KuduClient.KuduClientBuilder("localhost");
> KuduClient client = b.build();
> KuduTable table = client.openTable("read_mode_test");
> KuduScannerBuilder scannerBuilder = client.newScannerBuilder(table);
> scannerBuilder.readMode(AsyncKuduScanner.ReadMode.READ_YOUR_WRITES);
> KuduScanner scanner = scannerBuilder.build();
> while (scanner.hasMoreRows()) {
> scanner.nextRows();
> }
> {noformat}
> I'm using Kudu at git hash a954418
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)