Skip to content
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

Jump to bottom

sysvar: add a note about tidb_service_scope #16356

Merged
merged 5 commits into from
Jan 29, 2024
Merged

sysvar: add a note about tidb_service_scope #16356

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
0fc2860
initial draft
hfxsd Jan 29, 2024
0341ac3
Update sql-statements/sql-statement-import-into.md
hfxsd Jan 29, 2024
6cac0c6
Apply suggestions from code review
hfxsd Jan 29, 2024
ac434e6
Update tidb-distributed-execution-framework.md
hfxsd Jan 29, 2024
2291730
Apply suggestions from code review
hfxsd Jan 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions system-variables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4933,6 +4933,7 @@ SHOW WARNINGS;
> **Note:**
>
> - If `tidb_service_scope` is not set for any TiDB node in a cluster, the DXF schedules all TiDB nodes to execute background tasks. If you are concerned about performance impact on current business, you can set `tidb_service_scope` to `background` for a few of the TiDB nodes. Only those nodes will execute background tasks.
> - It is strongly recommended to select two or more TiDB nodes in an environment with several TiDB nodes and set this system variable to `background`. If `tidb_service_scope` is set on a single TiDB node only, when the node is restarted or fails, the task will be rescheduled to other TiDB nodes that lack the `background` setting, which will affect these TiDB nodes.
hfxsd marked this conversation as resolved.
Show resolved Hide resolved
> - For newly scaled nodes, the DXF tasks are not executed by default to avoid consuming the resources of the scaled node. If you want this scaled node to execute background tasks, you need to manually set `tidb_service_scop` of this node to `background`.

### tidb_session_alias <span class="version-mark">New in v7.4.0</span>
Expand Down
1 change: 1 addition & 0 deletions tidb-distributed-execution-framework.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,7 @@ Adjust the following system variables related to Fast Online DDL:
> **Note:**
>
> - 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`.
hfxsd marked this conversation as resolved.
Show resolved Hide resolved
> - It is strongly recommended to select two or more TiDB nodes in an environment with several TiDB nodes and set this system variable to `background`. If `tidb_service_scope` is set on a single TiDB node only, when the node is restarted or fails, the task will be rescheduled to other TiDB nodes that lack the `background` setting, which will affect these TiDB nodes.
hfxsd marked this conversation as resolved.
Show resolved Hide resolved
> - 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.

## Implementation principles
Expand Down