New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
roachtest: weekly/tpcc/headroom failed #122439
Comments
Workload saw the following error
Which is the same error observed in last week's failure (#121997). This failure includes #122255, so I'm guessing that change didn't completely fix the issue. Reassigning to KV. |
@nvanbenschoten, coming back to this again, and I'm wondering if the issue here has to do with the ambiguous nature of the error being returned. The rationale behind why we're marking the error ambiguous is here: cockroach/pkg/kv/kvclient/kvcoord/dist_sender.go Lines 2972 to 2976 in f7178a4
That doesn't apply to pre-commit
I still don't follow the last bit about handling ambiguity in --- a/pkg/kv/kvclient/kvcoord/dist_sender.go
+++ b/pkg/kv/kvclient/kvcoord/dist_sender.go
@@ -1393,7 +1393,8 @@ func (ds *DistSender) divideAndSendParallelCommit(
// Send the batch with withCommit=true since it will be inflight
// concurrently with the EndTxn batch below.
- reply, pErr := ds.divideAndSendBatchToRanges(ctx, qiBa, qiRS, qiIsReverse, true /* withCommit */, qiBatchIdx)
+ // TODO(XXX): update comment ^.
+ reply, pErr := ds.divideAndSendBatchToRanges(ctx, qiBa, qiRS, qiIsReverse, false /* withCommit */, qiBatchIdx)
qiResponseCh <- response{reply: reply, positions: positions, pErr: pErr}
}); err != nil {
return nil, kvpb.NewError(err) |
In certain cases, requests may return an error after successful evaluation. One example is `IntentMissingErrors` returned by `QueryIntent` requests when the queried intent is missing. In such cases, from the perspective of the client, the request is successful. It shouldn't be retried on another replica and any state maintained from prior attempts should be forgotten. The former was already handled, likely by unintentionally. This patch fixes the latter. In particular, any ambiguous error tracking from previous attempts is forgotten, and in cases where the request evaluated successfully but returned an error, the error is no longer wrapped as ambiguous. Fixes cockroachdb#122439 Epic: none Release note: None
Removing the |
roachtest.weekly/tpcc/headroom failed with artifacts on master @ c4ab095c4f65b9140661ed57adddc690b1e3ce3f:
Parameters:
|
roachtest.weekly/tpcc/headroom failed with artifacts on master @ f117eea22dd7be380c7141cdf6cd7aba92dd9c70:
Parameters:
ROACHTEST_arch=amd64
ROACHTEST_cloud=gce
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=16
ROACHTEST_encrypted=true
ROACHTEST_fs=ext4
ROACHTEST_localSSD=true
ROACHTEST_metamorphicBuild=false
ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
See: Grafana
This test on roachdash | Improve this report!
Jira issue: CRDB-37891
The text was updated successfully, but these errors were encountered: