From ca54bcaa04f037d55e9b91d357d94a6d69502ce5 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Tue, 14 Nov 2023 11:38:14 +0800 Subject: [PATCH] tidb: `tidb_service_scope` GA (#15226) --- system-variables.md | 4 ---- tidb-distributed-execution-framework.md | 6 +++--- 2 files changed, 3 insertions(+), 7 deletions(-) diff --git a/system-variables.md b/system-variables.md index 2d910173f75c8..9bc82ff868e9a 100644 --- a/system-variables.md +++ b/system-variables.md @@ -4821,10 +4821,6 @@ SHOW WARNINGS; ### tidb_service_scope New in v7.4.0 -> **Warning:** -> -> This feature is an experimental feature. It is not recommended to use it in production environments. 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) on GitHub. - - Scope: GLOBAL diff --git a/tidb-distributed-execution-framework.md b/tidb-distributed-execution-framework.md index 9838b72e36cef..469cd7d6ab555 100644 --- a/tidb-distributed-execution-framework.md +++ b/tidb-distributed-execution-framework.md @@ -118,10 +118,10 @@ Adjust the following system variables related to Fast Online DDL: * [`tidb_ddl_reorg_batch_size`](/system-variables.md#tidb_ddl_reorg_batch_size): use the default value. The recommended maximum value is `1024`. 3. Starting from v7.4.0, you can adjust the number of TiDB nodes that perform background tasks according to actual needs. After deploying a TiDB cluster, you can set the instance-level system variable [`tidb_service_scope`](/system-variables.md#tidb_service_scope-new-in-v740) for each TiDB node in the cluster. When `tidb_service_scope` of a TiDB node is set to `background`, the TiDB node can execute background tasks. When `tidb_service_scope` of a TiDB node is set to the default value "", the TiDB node cannot execute background tasks. If `tidb_service_scope` is not set for any TiDB node in a cluster, the TiDB distributed execution framework schedules all TiDB nodes to execute background tasks by default. - - > **Warning:** + > **Note:** > - > `tidb_service_scope` is an experimental feature. It is not recommended to use it in production environments. 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) on GitHub. + > - During the execution of a distributed task, if some TiDB nodes are offline, the distributed task randomly assigns subtasks to available TiDB nodes instead of dynamically assigning subtasks according to `tidb_service_scope`. + > - During the execution of a distributed task, changes to the `tidb_service_scope` configuration will not take effect for the current task, but will take effect from the next task. > **Tip:** >