You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
pd: note that the scheduling microservice does not support label-property - #22016
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign lance6716 for approval. For more information see the Code Review Process. Please ensure that each of them provides their approval before proceeding.
The full list of commands accepted by this bot can be found here.
Details
Needs approval from an approver in each of these files:
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Finishing Touches
🧪 Generate unit tests (beta)
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
lhy1024
changed the title
pd: 说明 scheduling 微服务不支持 label-property
pd: note that the scheduling microservice does not support label-property
Oct 29, 2026
Reviewing files that changed from the base of the PR and between ced4dbc and 51b88e2.
Files selected for processing: 1
pd-microservices.md
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.
<source_evidence>
<source kind="open_page">
<title>pd: note that the scheduling microservice does not support label-property by lhy1024 · Pull Request #24593 · pingcap/docs · GitHub</title>
<location>GitHub pull request 24593 in pingcap/docs (link omitted to avoid creating a cross-reference)</location>
<excerpt>citeturn1view0 [wordlim: 200] Crawled: today; Content type: text/html; Source: open({"ref_id":"https://github.com/pingcap/docs/pull/24593","lineno":null}); Total lines: 326
L0: 【0†Skip to content】
L1: ## Navigation Menu
L2:
L3: * Products
L4:
L5: * * 【1†GitHubRepository hosting, code review, and collaboration】
L6: * 【2†CopilotAI coding agent for tasks, projects and automated work】
L7:
L8: * Build & Ship
L9: * 【3†ActionsCI/CD and automation】
L10: * 【4†Code QualityQuality analysis, fixes, and enforcement】
L11: * 【5†CodespacesCloud development environments】
L12:
L13: * Secure
L14: * 【6†Code SecurityVulnerability detection and remediation】
L15: * 【7†Secret ProtectionSecret scanning and leak prevention】
L16: 【8†All Features】
L17:
L18: * Developers
L19:
L20: * Learn
L21: * 【9†Documentation†docs.github.com】
L22: * 【10†Training†learn.github.com】
L23: * 【11†Certifications†learn.github.com】
L24:
L25: * Build
L26: * 【12†Build with Copilot】
L27: * 【13†Customize Copilot†docs.github.com】
L28: * 【14†Integrations】
L29:
L30: * Explore
L31: * 【15†Trending repos】
L32: * 【16†GitHub Sponsors】
L33: * 【17†Events】
L34: * * 【18†ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.†github.blog】
L35:
L36: * Businesses
L37:
L38: * By Stage
L39: * 【19†Enterprises】
L40: * 【20†Team】
L41: * 【21†Startups】
L42: * 【22†Nonprofits】
L43:
L44: * By Industry
L45: * 【23†Healthcare】
L46: * 【24†Financial services】
L47: * 【25†Manufacturing】
L48: * 【26†Government】
L49: * 【27†See all industries】
L50: * Evaluate GitHub
L51: * 【28†Why GitHub】
L52: * 【29†Customer Stories】
L53: * 【30†Business insights】
L54: * 【31†Trust Center】
L55:
L56: * Add-ons
L57: * 【32†GitHub Advanced SecurityEnterprise-grade code security】
L58: * 【33†Copilot for businessEnterprise-grade AI features】
L59: * 【34†Premium SupportEnterprise-grade 24/7 support】
L60:
L61: * Resources
L62: * Learn & Connect
L63: * 【9†Documentation†docs.github.com】
L64: * 【35†Resource center】
L65: * 【36†Blog†github.blog】
L66: * 【17†Events & webinars】
L67: * 【37†Community Forum】
L68: * 【29†Customer Stories】
L69: * 【14†Integrations】
L70:
L71: * Support
L72: * 【38†Customer support†help.github.com】
L73: * 【10†Training†learn.github.com】
L74: * 【39†GitHub Status†www.githubstatus.com】
L75:
L76: * Company
L77: * 【40†About】
L78: * 【41†Partners】
L79: * 【18†Changelog†github.blog】
L80: * * 【42†GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.†githubuniverse.com】
L81:
L82: * 【43†Pricing】
L83:
L84: Search`/`
L85:
L86: 【44†Sign in】
L87:
L88: 【45†Sign up】
L89:
L90: Appearance settings
L91:
L92: You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
L93:
L94: 1. 【46†pingcap】
L95: 2. 【47†docs】
L96: ## Repository navigation
L97:
L98: * * 【47†Code】
L99: * 【48†Issues173 (173)】
L100: * 【49†Pull requests178 (178)】
L101: * 【50†Actions】
L102: * 【51†Projects】
L103: * 【52†Security and quality】
L104: * 【53†Insights】
L105:
L106: More items
L107:
L108: # pd: note that the scheduling microservice does not support label-property - #24593
L109: #24593
L110:
L111: Open
L112:
L113: 【54†lhy1024】 wants to merge 1 commit into
L114:
L115: 【55†pingcap:master】pingcap/docs:master from
L116:
L117: 【56†lhy1024:pd-microservices-label-property】lhy1024/docs:pd-microservices-label-property Copy head branch name to clipboard
L118:
L119: 【57†Conversation】【58†Commits1 (1)】【59†Checks】【60†Files changed】
L120:
L121: Open
L122: ##
L123:
L124: 【61†pd: note that the scheduling microservice does not support label-property】#24593
L125:
L126: 【54†lhy1024】 wants to merge 1 commit into
L127:
L128: 【55†pingcap:master】pingcap/docs:master from
L129:
L130: 【56†lhy1024:pd-microservices-label-property】lhy1024/docs:pd-microservices-label-property Copy head branch name to clipboard
L131:
L132: ## Conversation
L133:
L134: ###
L135:
L136: 【62†Image: @lhy1024†avatars.githubusercontent.com】 【54†lhy1024】 commented 【63†Oct 29, 2026】 •
L137:
L138: edited
L139:
L140: Loading
L141: ### Uh oh!
L142:
L143: There was an error while loading. Please reload this page.
L144:
L145: Copy link
L146:
L147: Copy Markdown
L148:
L149: ### What is changed, added, or deleted? (Required)
L150:
L151: Clarify that the `scheduling` microservice does not support the deprecated `label-property` configuration. Add this restriction to the PD microservices page and add a note to the `label-property` section recommending Placement Rules or `evict-leader-scheduler` to keep leaders off specific stores.
L152: ### Which TiDB version(s) do your changes apply to? (Required)
L153:
L154: * [Input] master (the latest development version)
L155: * [Input] v9.0 (TiDB 9.0 versions)
L156: * [Input] v8.5 (TiDB 8.5 versions)
L157: * [Input] v8.1 (TiDB 8.1 versions)
L158: * [Input] v7.5 (TiDB 7.5 versions)
L159: * [Input] v7.1 (TiDB 7.1 versions)
L160: * [Input] v6.5 (TiDB 6.5 versions)
L161: ### What is the related PR or file link(s)?
L162:
L163: * Related code change PR links (if applicable): 【64†mcs: sync the label property to the scheduling service tikv/pd#11444】
L164: * This PR is translated from: 【65†pd: 说明 scheduling 微服务不支持 label-property docs-cn#22016】
L165: * Other reference link(s): 【66†mcs: the scheduling service ignores label properties such as reject-leader tikv/pd#11443】
L166:
L167: ### AI agent involvement
L168:
L169: * [Input] The changes in this PR were primarily made by an AI agent on behalf of the PR author.
L170: ### Do your changes match any of the following descriptions?
L171:
L172: * [Input] Delete files
L173: * [Input] Change aliases
L174: * [Input] Need modification after applied to another branch
L175: * [Input] Might cause conflicts after applied to another branch
L176:
L177: [Input][Input]
L178:
L179: Sorry, something went wrong.
L180: ### Uh oh!
L181:
L182: There was an error while loading. Please reload this page.
L183:
L184: ` 【67†docs: clarify label-property support in PD microservices】 ` [Button: … ]
L185:
L186: [Input] [Input] [Input]
L187:
L188: ` 【67†a8978f7】 `
L189:
L190: Signed-off-by: lhy1024 <19542290+lhy1024@users.noreply.github.com>
L191: ###
L192:
L193: 【68†ti-chi-bot】 Bot commented 【69†Oct 29, 2026】
L194:
L195: Copy link
L196:
L197: Copy Markdown
L198: [APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by:
L199: Once this PR has been reviewed and has the lgtm label, please assign 【70†kissmydb】 for approval. For more information see 【71†the Code Review Process†book.prow.tidb.net】.
L200: Please ensure that each of them provides their approval before proceeding. The full list of commands accepted by this bot can be found 【72†here†prow.tidb.net】. Details Needs approval from an approver in each of these files:
L201: * 【73†OWNERS】
L202: Approvers can indicate their approval by writing `/approve` in a comment
L203: Approvers can cancel approval by writing `/approve cancel` in a comment
L204:
L205: [Input][Input]
L206:
L207: Sorry, something went wrong.
L208: ### Uh oh!
L209:
L210: There was an error while loading. Please reload this page.
L211:
L212: 【68†ti-chi-bot】 Bot added the 【74†missing-translation-status】 This PR does not have translation status info. label 【75†Oct 29, 2026】
L213:
L214: 【54†lhy1024】 mentioned this pull request 【76†Oct 29, 2026】
L215:
L216: 【65†pd: 说明 scheduling 微服务不支持 label-property pingcap/docs-cn#22016】
L217:
L218: Open
L219:
L220: 4 of 12 tasks
L221:
L222: 【68†ti-chi-bot】 Bot added the 【77†size/XS】 Denotes a PR that changes 0-9 lines, ignoring generated files. label 【78†Oct 29, 2026】
L223: ###
L224:
L225: 【79†coderabbitai】 Bot commented 【80†Oct 29, 2026】
L226:
L227: Copy link
L228:
L229: Copy Markdown
L230:
L231: Note Currently processing new changes in this PR. This may take a few minutes, please wait... 【81†Image†camo.githubusercontent.com】 Run configuration
L232: * Source mode: Auto
L233: * Repository: 【47†pingcap/docs】
L234: * Branch: 【55†master】
L235: * File: 【82†.coderabbit.yaml】
L236: * Commit: 【83†e5e80ae】
L237: * Layers: Repository YAML
L238: * Review profile: ASSERTIVE
L239: * Plan: Advanced
L240: * Run ID: `95f456ba-cfc9-436f-be51-0f85f43d7270`
L241: 【84†Image†camo.githubusercontent.com】 Commits
L242:
L243: Reviewing files that changed from the base of the PR and between 【83†`e5e80ae`】 and 【85†`a8978f7`】.
L244: 【86†Image†camo.githubusercontent.com】 Files selected for processing: 2
L245: * `pd-configuration-file.md`
L246: * `pd-microservices.md`
L247: Finishing Touches
L248:
L249: 🧪 Generate unit tests (beta)
L250:
L251:
L252:
L253: * [Input] Create a new PR
L254:
L255: * [Input] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
L256: Thanks for using 【87†CodeRabbit†coderabbit.ai】! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. ❤️ Share
L257: * 【88†X†twitter.com】
L258: * 【89†Mastodon†mastodon.social】
L259: * 【90†Reddit†www.reddit.com】
L260: * 【91†LinkedIn†www.linkedin.com】
L261: _{Comment `@coderabbitai help` to get the list of available commands.}
L262:
L263: [Input][Input]
L264:
L265: Sorry, something went wrong.
L266: ### Uh oh!
L267:
L268: There was an error while loading. Please reload this page.
L269:
L270: 【54†lhy1024】 added 【92†needs-cherry-pick-release-8.1】 Should cherry pick this PR to release-8.1 branch. 【93†needs-cherry-pick-release-8.5】 Should cherry pick this PR to release-8.5 branch. labels 【94†Oct 29, 2026】
L271:
L272: This was referenced Oct 29, 2026
L273:
L274: 【64†mcs: sync the label property to the scheduling service tikv/pd#11444】
L275:
L276: Closed
L277:
L278: 【66†mcs: the scheduling service ignores label properties such as reject-leader tikv/pd#11443】
L279:
L280: Closed
L281: 【95†Sign up for free】 to join this conversation on GitHub. Already have an account? 【44†Sign in to comment】
L282:
L283: [Input] [Input]
L284: ### Reviewers
L285:
L286: No reviews
L287:
L288: ### Uh oh!
L289:
L290: There was an error while loading. Please reload this page.
L291:
L292: [Input][Input]
L293:
L294: ### Assignees
L295:
L296: No one assigned
L297:
L298: ### Labels
L299:
L300: 【74†missing-translation-status】 This PR does not have translation status info. 【92†needs-cherry-pick-release-8.1】 Should cherry pick this PR to release-8.1 branch. 【93†needs-cherry-pick-release-8.5】 Should cherry pick this PR to release-8.5 branch. 【77†size/XS】 Denotes a PR that changes 0-9 lines, ignoring generated files.
L301:
L302: [Input][Input]
L303: ### Projects
L304:
L305: None yet
L306:
L307: [Input][Input]
L308:
L309: ### Milestone
L310:
L311: No milestone
L312:
L313: [Input][Input]
L314:
L315: ### Development
L316:
L317: Successfully merging this pull request may close these issues.
L318:
L319: ### Uh oh!
L320:
L321: There was an error while loading. Please reload this page.
L322: ### 1 participant
L323: Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now.
L324: Please check back later.
L325: You can’t perform that action at this time.
</excerpt>
</source>
<source kind="search">
<title>PD Microservices - dev | TiDB Docs</title>
<location>https://docs.pingcap.com/tidb/dev/pd-microservices/</location>
<excerpt>citeturn0search0 [wordlim: 200] Crawled: 2 months ago; If the binary versions of the `scheduling` microservice and PD are different, to prevent changes in the scheduling logic, you can disable the dynamic switching function of the `scheduling` microservice by executing `pd-ctl config set enable-scheduling-fallback false`.
* The `scheduling` microservice supports dynamic switching, which is enabled by default (`enable-scheduling-fallback` defaults to `true`). If the process of the `scheduling` microservice is terminated, PD continues to provide scheduling services for the cluster by default.
If the binary versions of the `scheduling` microservice and PD are different, to prevent changes in the scheduling logic, you can disable the dynamic switching function of the `scheduling` microservice by executing `pd-ctl config set enable-scheduling-fallback false`. After this function is disabled, PD will not take over the scheduling service when the process of the `scheduling` microservice is terminated. This means that the scheduling service of the cluster will be unavailable until the `scheduling` microservice is restarted.
## Tool compatibility
Microservices do not affect the normal use of data import, export, and other replication tools.
## FAQs
* How can I determine if PD becomes a performance bottleneck?
When your cluster is in a normal state, you can check monitoring metrics in the Grafana PD panel. If the `TiDB - PD server TSO handle time` metric shows a notable increase in latency or the `Heartbeat - TiKV side heartbeat statistics` metric shows a significant number of pending items, it indicates that PD becomes a performance bottleneck.</excerpt>
</source>
<source kind="search">
<title>GitHub - pingcap/docs: TiDB database documentation. TiDB is an open-source, cloud-native, distributed, MySQL-Compatible database for elastic scale and real-time analytics. · GitHub</title>
<location>https://github.com/pingcap/docs</location>
<excerpt>citeturn0search1 [wordlim: 200] Crawled: last month; If you find documentation issues, feel free to create an Issue to let us know or directly create a Pull Request to help fix or update it. ... docs.pingcap.com
# TiDB Documentation
Welcome to TiDB documentation!
This repository stores all the source files of TiDB Docs at the PingCAP website, while the pingcap/docs-cn repository stores all the source files of TiDB Documentation in Chinese.
If you find documentation issues, feel free to create an Issue to let us know or directly create a Pull Request to help fix or update it.
If you want to locally customize and output TiDB documentation in PDF format to meet the needs of specific scenarios, such as freely sorting or deleting certain contents in TiDB documentation, please refer to TiDB Documentation PDF Generation Tutorial.
Currently, the official documentation supports two languages:
* `en`: documentation in English
* `zh`: documentation in Chinese
You can use Google Translate to view the documentation in different languages. For example:
</excerpt>
</source>
<source kind="search">
<title>docs/dynamic-config.md at master · pingcap/docs · GitHub</title>
<location>https://github.com/pingcap/docs/blob/master/dynamic-config.md</location>
<excerpt>citeturn0search2 [wordlim: 200] Crawled: last week; Currently, PD does not support the separate configuration for each instance. ... If a configuration item is successfully modified, the result is persisted in etcd instead of in the configuration file; the configuration in etcd will prevail in the subsequent operations. ... `schedule.leader-schedule-policy` | Determines the policy of Leader scheduling ... `schedule.enable-joint-consensus` | Controls whether to use Joint Consensus for replica scheduling ... `replication.strictly-match-label` | Enables the label check
`schedule.replica-schedule-limit` | The number of Replica scheduling tasks performed at the same time
`schedule.merge-schedule-limit` | The number of the `Region Merge` scheduling tasks performed at the same time
`schedule.hot-region-schedule-limit` | The number of hot Region scheduling tasks performed at the same time
`schedule.hot-region-cache-hits-threshold` | Determines the threshold at which a Region is considered a hot spot
`schedule.high-space-ratio` | The threshold ratio below which the capacity of the store is sufficient
`schedule.low-space-ratio` | The threshold ratio above which the capacity of the store is insufficient
`schedule.tolerant-size-ratio` | Controls the `balance` buffer size
`schedule.enable-remove-down-replica` | Determines whether to enable the feature that automatically removes `DownReplica`
`schedule.enable-replace-offline-replica` | Determines whether to enable the feature that migrates `OfflineReplica`
`schedule.enable-make-up-replica` | Determines whether to enable the feature that automatically supplements replicas
`schedule.enable-remove-extra-replica` | Determines whether to enable the feature that removes extra replicas
`schedule.enable-location-replacement` | Determines whether to enable isolation level check
`schedule.enable-cross-table-merge` | Determines whether to enable cross-table merge
`schedule.enable-one-way-merge` | Enables one-way merge, which only allows merging with the next adjacent Region
`schedule.region-score-formula-version` | Controls the version of the Region score formula
`schedule.scheduler-max-waiting-operator` | Controls the number of waiting operators in each scheduler
`schedule.enable-debug-metrics` | Enables the metrics for debugging
`schedule.enable-heartbeat-concurrent-runner` | Enables asynchronous concurrent processing for Region heartbeats
`schedule.enable-heartbeat-breakdown-metrics` | Enables breakdown metrics for Region heartbeats to measure the time consumed in each stage of Region heartbeat processing
`schedule.enable-joint-consensus` | Controls whether to use Joint Consensus for replica scheduling
`schedule.hot-regions-write-interval` | The time interval at which PD stores hot Region information
`schedule.hot-regions-reserved-days` | Specifies how many days the hot Region information is retained
`schedule.max-movable-hot-peer-size` | Controls the maximum Region size that can be scheduled for hot Region scheduling.
`schedule.store-limit-version` | Controls the version of store limit
`schedule.patrol-region-worker-count` | Controls the number of concurrent operators created by the checker when inspecting the health state of a Region
`replication.max-replicas` | Sets the maximum number of replicas
`replication.location-labels` | The topology information of a TiKV cluster
`replication.enable-placement-rules` | Enables Placement Rules
`replication.strictly-match-label` | Enables the label check
`replication.isolation-level` | The minimum topological isolation level of a TiKV cluster
`pd-server.use-region-storage` | Enables independent Region storage
`pd-server.max-gap-reset-ts` | Sets the maximum interval of resetting timestamp (BR)
</excerpt>
</source>
<source kind="search">
<title>Pull requests · pingcap/docs · GitHub</title>
<location>https://github.com/pingcap/docs/pulls</location>
<excerpt>citeturn0search3 [wordlim: 200] Crawled: 2 months ago; # Pull requests: pingcap/docs
pingcap / docs Public
* Notifications You must be signed in to change notification settings
* Fork 717
* Star
* Code
* Issues 141
* Pull requests 135
* Actions
* Projects
* Security and quality 0
* Insights
Additional navigation options
# Pull requests: pingcap/docs
[Input: Search all issues]
Labels Milestones
New
135 Open 21,320 Closed
## Pull requests list
cloud: add changefeed OSS configuration for premium. area/tidb-cloud This PR relates to the area of TiDB Cloud. contribution This PR is from a community contributor. for-cloud-release This PR is related to TiDB Cloud release. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. translation/no-need No need to translate this PR.
#23585 opened Aug 20, 2026 by ginkgoch Collaborator
9
i18n(ja): fix だ/である plain-style sentences stranded in polite prose area/develop This PR relates to the area of TiDB App development. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. missing-translation-status This PR does not have translation status info. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
#23584 opened Aug 20, 2026 by yahonda Member
3
docs: unify "standardized" to "normalized" for SQL statements in sql-plan-management.md missing-translation-status This PR does not have translation status info. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
#23581 opened Aug 20, 2026 by yahonda Member
3
i18n(ja): fix dropped particles before common action verbs area/develop This PR relates to the area of TiDB App development. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. translation/no-need No need to translate this PR.
</excerpt>
</source>
<omitted_sources count="13">Additional source records were omitted from this bounded result.</omitted_sources>
</source_evidence>
Citations:
- 1: GitHub pull request 24593 in pingcap/docs (link omitted to avoid creating a cross-reference)
- 2: GitHub pull request 24593 in pingcap/docs (link omitted to avoid creating a cross-reference)
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is changed, added, or deleted? (Required)
在 PD 微服务使用限制和
label-property配置说明中补充:scheduling微服务不支持已废弃的label-property,需要让 Leader 不调度到特定 store 时应使用 Placement Rules 或evict-leader-scheduler。Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?
Summary by CodeRabbit
scheduling微服务时不支持已废弃的label-property配置,reject-leader类型也不生效。evict-leader-scheduler。scheduling微服务,且 PD 通过默认开启的enable-scheduling-fallback自行调度,label-property配置仍会生效。