docs: clarify max-ts max-drift constraint#21761
Conversation
Signed-off-by: Ziqian Qin <eke@fastmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Pull request overview
Clarifies the TiKV storage.max-ts.max-drift configuration constraint to prevent invalid configurations (where max-drift is not greater than cache-sync-interval) from being used.
Changes:
- Document that
storage.max-ts.max-driftmust be greater thanstorage.max-ts.cache-sync-interval, otherwise TiKV rejects loading the configuration. - Keep the existing recommendation to set
max-driftto at least 3×cache-sync-interval.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: Ziqian Qin <eke@fastmail.com>
What is changed, added or deleted? (Required)
Clarify that
storage.max-ts.max-driftmust be greater thancache-sync-interval, otherwise TiKV rejects the configuration.Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?