Skip to content

Commit 445741d

Browse files
authored
tidb: add description for var tidb_ddl_reorg_max_write_speed (#19445)
1 parent 4f968f2 commit 445741d

1 file changed

Lines changed: 11 additions & 0 deletions

File tree

system-variables.md

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

1698+
### tidb_ddl_reorg_max_write_speed <span class="version-mark">New in v8.5.0</span>
1699+
1700+
- Scope: GLOBAL
1701+
- Persists to cluster: Yes
1702+
- Applies to hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value): No
1703+
- Type: Integer
1704+
- Default value: `0`
1705+
- Range: `[0, 1125899906842624]` (the maximum value that can be set is 1 PiB)
1706+
- 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.
1707+
- 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'`.
1708+
16981709
### tidb_ddl_reorg_worker_cnt
16991710

17001711
> **Note:**

0 commit comments

Comments
 (0)