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
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
wojcik-dorota
changed the title
feat: add mudumper / myloader as an alternative mysql migration tool
feat: add MySQL mydumper / myloader as a migration tool
Sep 11, 2025
wojcik-dorota
changed the title
feat: add MySQL mydumper / myloader as a migration tool
feat: add MySQL mydumper / myloader migration tool
Sep 11, 2025
ORR review follow up:
re: a large migration could consume all resources for hours and even days
Agree that this is probably unavoidable — we’ll probably want documentation/user guides that strongly recommend overspec’ing the node for the migration
Also during my testing I noticed that mydumper really better only on very large plans. @wojcik-dorota could you add to documentation that we recommend using large plans for migration with mydumper?
ORR review follow up: re: a large migration could consume all resources for hours and even days
Agree that this is probably unavoidable — we’ll probably want documentation/user guides that strongly recommend overspec’ing the node for the migration
Also during my testing I noticed that mydumper really better only on very large plans. @wojcik-dorota could you add to documentation that we recommend using large plans for migration with mydumper?
Thanks, @VitaliVinahradski ! Since we're moving away from the "service plan" terminology, I'll try to say the same using "multiple nodes", "large RAM", or similar. Any recommendations for the wording without "service plans"?
I think main requirement was number of CPUs and RAM. Mydumper runs on single node (master).
To prevent performance bottlenecks while migrating large database, we recommend choosing a service configuration with significant computational power (multiple vCPUs) and high memory capacity.
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.
github-actions
bot
added
service/mysql
platform
tech
wojcik-dorota
changed the title
JIRA
DOC PREVIEWs:
Checklist
/docs/.