Skip to content

cloud: update tidb_dml_type limitation (#22415) #22418

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

Open
ti-chi-bot wants to merge 2 commits into
base: master
Choose a base branch
from
+5 −0
Open

cloud: update tidb_dml_type limitation (#22415) #22418

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5ebdbe0
update tidb_dml_type limitation
zuowei593 Feb 6, 2026
724efdb
add a note in system-variables.md indicating that this variable is re…
qiancai Feb 6, 2026
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
4 changes: 4 additions & 0 deletions system-variables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1954,6 +1954,10 @@ Assume that you have a cluster with 4 TiDB nodes and multiple TiKV nodes. In thi
>
> The bulk DML execution mode (`tidb_dml_type = "bulk"`) is an experimental feature. It is not recommended that you use it in the production environment. This feature might be changed or removed without prior notice. If you find a bug, you can report an [issue](https://github.com/pingcap/tidb/issues). In the current version, when TiDB performs large transactions using the bulk DML mode, it might affect the memory usage and execution efficiency of TiCDC, TiFlash, and the resolved-ts module of TiKV, and might cause OOM issues. Additionally, BR might be blocked and fail to process when encountering locks. Therefore, it is not recommended to use this mode when these components or features are enabled.

> **Note:**
>
> This variable is read-only for [{{{ .starter }}}](https://docs.pingcap.com/tidbcloud/select-cluster-tier#starter) and [{{{ .essential }}}](https://docs.pingcap.com/tidbcloud/select-cluster-tier#essential).
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

For better readability and consistency with other notes in this document, consider rephrasing this sentence.

Suggested change
> This variable is read-only for [{{{ .starter }}}](https://docs.pingcap.com/tidbcloud/select-cluster-tier#starter) and [{{{ .essential }}}](https://docs.pingcap.com/tidbcloud/select-cluster-tier#essential).
> For [{{{ .starter }}}](https://docs.pingcap.com/tidbcloud/select-cluster-tier#starter) and [{{{ .essential }}}](https://docs.pingcap.com/tidbcloud/select-cluster-tier#essential) clusters, this variable is read-only.
References
  1. The documentation should be easy to understand for TiDB users. Rephrasing the sentence improves clarity and readability. (link)


- Scope: SESSION
- Applies to hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value): Yes
- Type: String
Expand Down
1 change: 1 addition & 0 deletions tidb-cloud/limited-sql-features.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,6 +142,7 @@ TiDB Cloud works with almost all workloads that TiDB supports, but there are som
| `tidb_ddl_reorg_batch_size` | No limitation | Read-only [^10] |
| `tidb_ddl_reorg_priority` | No limitation | Read-only [^10] |
| `tidb_ddl_reorg_worker_cnt` | No limitation | Read-only [^10] |
| `tidb_dml_type` | No limitation | Read-only [^10] |
| `tidb_enable_1pc` | No limitation | Read-only [^10] |
| `tidb_enable_async_commit` | No limitation | Read-only [^10] |
| `tidb_enable_auto_analyze` | No limitation | Read-only [^10] |
Expand Down