sql: inconsistent scan can return error cannot specify timestamp older than 5m0s for this operation
if cluster is overloaded
#100304
Labels
A-sql-table-stats
Table statistics (and their automatic refresh).
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
E-quick-win
Likely to be a quick win for someone experienced.
O-support
Would prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docs
P-3
Issues/test failures with no fix SLA
T-sql-queries
SQL Queries Team
The following error can observed in a cluster that is under a lot of load:
This seems easy to reproduce by setting up a cluster and running
tpcc
with more warehouses than the cluster can comfortably handle. For reference, I saw a couple of occurrences of this error in a 4-node (n1-standard-4
) cluster with 200 warehouses.Likely not relevant: the error above happened while in a mixed-version state. I don't think this is related, but worth pointing out. It has also been seen in roachtests before (coincidentally or not, in another mixed version test): #93623 (comment)
Jira issue: CRDB-26361
The text was updated successfully, but these errors were encountered: