docs: block cluster pause when PITR or Data Migration is active - #23402
docs: block cluster pause when PITR or Data Migration is active#23402xboxeer wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pause and resume documentation now states that users must disable PITR or stop a running Data Migration job before pausing a TiDB cluster. ChangesPause Restrictions
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
[LGTM Timeline notifier]Timeline:
|
|
[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 |
What's changed
Clusters with Point-in-Time Restore (PITR) enabled or a Data Migration job running can no longer be paused directly. The pause request is rejected with a clear error until users explicitly disable PITR / stop the migration job.
Documentation changes
Adds two new bullets to the Limitations section of
tidb-cloud/pause-or-resume-tidb-cluster.md.Summary by CodeRabbit