Skip to content

add a note to automatic retry #21927

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.

Sign up for GitHub

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

Merged
merged 5 commits into from
Oct 17, 2025
Merged

add a note to automatic retry #21927

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
fd852ab
Update optimistic-transaction.md
hfxsd Oct 16, 2025
09ede06
Update optimistic-transaction.md
hfxsd Oct 16, 2025
8f76cef
Update optimistic-transaction.md
hfxsd Oct 16, 2025
300e0cc
Update optimistic-transaction.md
hfxsd Oct 16, 2025
580804d
Update optimistic-transaction.md
hfxsd Oct 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion optimistic-transaction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,10 +69,15 @@
>
> Starting from v8.0.0, the [`tidb_disable_txn_auto_retry`](/system-variables.md#tidb_disable_txn_auto_retry) system variable is deprecated, and TiDB no longer supports automatic retries of optimistic transactions. It is recommended to use the [Pessimistic transaction mode](/pessimistic-transaction.md). If you encounter optimistic transaction conflicts, you can capture the error and retry transactions in your application.

In the optimistic transaction model, transactions might fail to be committed because of write–write conflict in heavy contention scenarios. Starting from v3.0.8, TiDB uses the [pessimistic transaction mode](/pessimistic-transaction.md) by default, the same as MySQL. This means that TiDB and MySQL add locks during the execution of write-type SQL statements, and its Repeatable Read isolation level allows for current reads, so commits generally do not encounter exceptions. To lower the difficulty of adapting applications, TiDB provides an internal retry mechanism.
In the optimistic transaction model, transactions might fail to be committed because of write–write conflict in heavy contention scenarios. Starting from v3.0.8, TiDB uses the [pessimistic transaction mode](/pessimistic-transaction.md) by default, the same as MySQL. This means that TiDB and MySQL add locks during the execution of write-type SQL statements, and its Repeatable Read isolation level allows for current reads, so commits generally do not encounter exceptions.

Check failure on line 72 in optimistic-transaction.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[PingCAP.EnDash] Use an em dash ('—') instead of en dash ('–').

Raw Output:
{"message": "[PingCAP.EnDash] Use an em dash ('—') instead of en dash ('–').", "location": {"path": "optimistic-transaction.md", "range": {"start": {"line": 72, "column": 94}}}, "severity": "ERROR"}

### Automatic retry

> **Note:**
>
> - Starting from TiDB v3.0.0, the automatic retry of transactions is disabled by default, because it can **break the transaction isolation level**.
> - Starting from TiDB v8.0.0, automatic retries of optimistic transactions are no longer supported.

If a write-write conflict occurs during the transaction commit, TiDB automatically retries the SQL statement that includes write operations. You can enable the automatic retry by setting `tidb_disable_txn_auto_retry` to `OFF` and set the retry limit by configuring `tidb_retry_limit`:

```toml
Expand Down