Skip to content

docs: clarify operational differences between throttling and postponing cut-over (#1766) - #1767

Open
soepic1 wants to merge 4 commits into
github:masterfrom
soepic1:docs/clarify-postpone-vs-throttle-and-uuid-progress
Open

soepic1 wants to merge 4 commits into
github:masterfrom
soepic1:docs/clarify-postpone-vs-throttle-and-uuid-progress

Conversation

@soepic1

@soepic1 soepic1 commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

Resolves #1766

Description

This PR improves the operational documentation for large-scale migrations (100M+ rows / multi-hour executions):

  1. Throttling vs. Postponing Cut-Over: Adds a clear comparison table and best-practice operational workflow detailing why --postpone-cut-over-flag-file is preferred over long-term --throttle-additional-flag-file during scheduled maintenance windows (preventing MySQL wait_timeout disconnects while maintaining real-time binlog sync).
  2. UUID / String Primary Key Guidance: Documents progress percentage behavior (e.g., overshoot past 100% and ETA: due) on tables with lexicographical/UUID primary keys and explains how operators can verify boundary progress.

Related Issue

Closes #1766

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Proposal] Operational insights & ETA overshoot on large UUID-keyed tables (140M+ rows)

1 participant