A context canceled error is not treated as undetermined #20733
Labels
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
severity/major
sig/transaction
SIG:Transaction
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Run rw-register case with nemesis of random_kill,kill_pd_leader_5min,partition_one,subcritical_skews,big_skews,shuffle-leader-scheduler,shuffle-region-scheduler,random-merge-scheduler. Here is the test record.
We found that one of transaction failed with
context canceled
:But actually the transaction is committed successfully becasue
w(380,593)
has been read by other transactions.Thus the test failed because a G1a anomaly was found.
2. What did you expect to see? (Required)
TiDB should mark such an error as undetermined and return it to client.
3. What did you see instead (Required)
From the log of tidb-server, it didn't return a undetermined error.
4. What is your TiDB version? (Required)
release-4.0 @ 66ac9fc
The text was updated successfully, but these errors were encountered: