dm: add LOCK TABLES privilege note for managed MySQL sources (#21467)#21558
Merged
ti-chi-bot[bot] merged 2 commits intopingcap:release-8.5from Apr 17, 2026
Merged
Conversation
ti-chi-bot
added
area/develop
2 tasks
qiancai
approved these changes
Apr 17, 2026
Collaborator
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is an automated cherry-pick of #21467
This PR is translated from: pingcap/docs#22605
What is changed, added or deleted?
Added conditional
LOCK TABLESprivilege documentation for managed MySQL sources (Amazon RDS, Aurora, Google Cloud SQL) across three DM docs pages.Background: DM defaults to
consistency=auto. On managed MySQL whereFLUSH TABLES WITH READ LOCKis restricted by the cloud provider, DM falls back toLOCK TABLES. This privilege is not needed on self-managed MySQL instances. Confirmed with @GMHDBJD (Minghao Guo): the FTWRL → LOCK TABLES fallback inautomode is by design.Changes:
dm/dm-precheck.md: Clarified thatLOCK TABLESis needed forautofallback on managed MySQL, not justflush/lockdm/dm-worker-intro.md: AddedLOCK TABLESto privilege table with managed-MySQL scope note; added conditional GRANT exampledm/quick-start-with-dm.md: Added note pointing to dm-worker-intro for managed MySQL sources (×2 instances)Evidence: Lab-06: LOCK TABLES privilege testing (9 scenarios, vanilla MySQL vs RDS)
Related:
Which TiDB version(s) do your changes apply to?
cc @GMHDBJD @qiancai @OliverS929