Skip to content

pd: note that the scheduling microservice does not support label-property #24593

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
lhy1024 wants to merge 3 commits into
base: master
Choose a base branch
from
+3 −0
Open

pd: note that the scheduling microservice does not support label-property #24593

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a8978f7
docs: clarify label-property support in PD microservices
lhy1024 Oct 29, 2026
f489d07
remove the trailing newlines added by mistake
lhy1024 Oct 29, 2026
cf4d1e3
docs: document label-property fallback
lhy1024 Oct 29, 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
2 changes: 2 additions & 0 deletions pd-configuration-file.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -496,6 +496,8 @@ Configuration items related to labels, which only support the `reject-leader` ty
> **Note:**
>
> Starting from v5.2, the configuration items related to labels are deprecated. It is recommended to use [Placement Rules](/configure-placement-rules.md#scenario-2-place-five-replicas-in-three-data-centers-in-the-proportion-of-221-and-the-leader-should-not-be-in-the-third-data-center) to configure the replica policy.
>
> In PD microservice mode, the `scheduling` microservice does not support `label-property`. Use [Placement Rules](/configure-placement-rules.md) or `evict-leader-scheduler` instead.

### `key` (deprecated)

Expand Down
1 change: 1 addition & 0 deletions pd-microservices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,7 @@ In addition, when the scheduling module is changed, you can update the `scheduli
- Microservices are not compatible with the [Data Replication Auto Synchronous (DR Auto-Sync)](/two-data-centers-in-one-city-deployment.md) feature.
- Microservices are not compatible with the TiDB system variable [`tidb_enable_tso_follower_proxy`](/system-variables.md#tidb_enable_tso_follower_proxy-new-in-v530).
- Because [hibernate Regions](/tikv-configuration-file.md#hibernate-regions) might exist in a cluster, during a primary and secondary switchover of the `scheduling` microservice, the scheduling function of the cluster might be unavailable for a certain period (up to [`peer-stale-state-check-interval`](/tikv-configuration-file.md#peer-stale-state-check-interval), which is five minutes by default) to avoid redundant scheduling.
- The `scheduling` microservice does not support the deprecated `label-property` configuration, so `reject-leader` label properties do not take effect when the `scheduling` microservice is enabled. To keep leaders off specific stores, use [Placement Rules](/configure-placement-rules.md) or `evict-leader-scheduler`. If no `scheduling` microservice is available and PD schedules by itself through `enable-scheduling-fallback` (enabled by default), `label-property` takes effect again.

## Usage

Expand Down
Loading