Matthew Jacobs created KUDU-1869:
------------------------------------
Summary: Scans do not work with hybrid time disabled and snapshot
reads enabled
Key: KUDU-1869
URL: https://issues.apache.org/jira/browse/KUDU-1869
Project: Kudu
Issue Type: Bug
Components: consensus
Affects Versions: 1.2.0
Environment: Centos 6.6
kudu 1.2.0-cdh5.10.0
revision 01748528baa06b78e04ce9a799cc60090a821162
build type RELEASE
6 nodes, 5 tservers/impalads
Reporter: Matthew Jacobs
Priority: Critical
With {{-use_hybrid_clock=false}} and scanning with SNAPSHOT_READ, all scans
appear to be timing out with the following error message:
{code}
[vc0736.halxg.cloudera.com:21000] > SELECT COUNT(*) FROM
functional_kudu.alltypes;
Query: select COUNT(*) FROM functional_kudu.alltypes
Query submitted at: 2017-02-10 09:50:02 (Coordinator:
http://vc0736.halxg.cloudera.com:25000)
Query progress can be monitored at:
http://vc0736.halxg.cloudera.com:25000/query_plan?query_id=ff48eb0af82f057e:f2c1e2f800000000
WARNINGS:
Unable to open scanner: Timed out: unable to retry before timeout: Remote
error: Service unavailable: Timed out: could not wait for desired snapshot
timestamp to be consistent: Timed out waiting for ts: L: 3632307 to be safe
(mode: NON-LEADER). Current safe time: L: 3598991 Physical time difference:
None (Logical clock): Remote error: Service unavailable: Timed out: could not
wait for desired snapshot timestamp to be consistent: Timed out waiting for ts:
L: 3625836 to be safe (mode: NON-LEADER). Current safe time: L: 3593993
Physical time difference: None (Logical clock)
{code}
This is a severe issue for Impala which aims to keep SNAPSHOT_READ enabled.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
