Skip to content

Commit 575df9e

Browse files
authored
v7.5.5 tidb: add description for var tidb_ddl_reorg_max_write_speed (#19445) (#19643)
1 parent 5cf9b88 commit 575df9e

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

system-variables.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1659,6 +1659,17 @@ mysql> SELECT job_info FROM mysql.analyze_jobs ORDER BY end_time DESC LIMIT 1;
16591659
- This variable is used to set the priority of executing the `ADD INDEX` operation in the `re-organize` phase.
16601660
- You can set the value of this variable to `PRIORITY_LOW`, `PRIORITY_NORMAL` or `PRIORITY_HIGH`.
16611661

1662+
### tidb_ddl_reorg_max_write_speed <span class="version-mark">New in v7.5.5</span>
1663+
1664+
- Scope: GLOBAL
1665+
- Persists to cluster: Yes
1666+
- Applies to hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value): No
1667+
- Type: Integer
1668+
- Default value: `0`
1669+
- Range: `[0, 1125899906842624]` (the maximum value that can be set is 1 PiB)
1670+
- This variable limits the write bandwidth for each TiKV node and only takes effect when index creation acceleration is enabled (controlled by the [`tidb_ddl_enable_fast_reorg`](#tidb_ddl_enable_fast_reorg-new-in-v630) variable). When the data size in your cluster is quite large (such as billions of rows), limiting the write bandwidth for index creation can effectively reduce the impact on application workloads.
1671+
- The default value `0` means no write bandwidth limit. The default unit is bytes per second. You can also set the value in formats such as `'1GiB'` or `'256MiB'`.
1672+
16621673
### tidb_ddl_reorg_worker_cnt
16631674

16641675
> **Note:**

0 commit comments

Comments
 (0)