Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Note that GC Disabling is a must despite Dumpling's auto extend feature #16347

Merged
merged 7 commits into from
Feb 8, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update migrate-from-tidb-to-mysql.md
Tetsuya3850 authored Feb 7, 2024

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
commit 7d770a64b93370ce0103e959988d70aa0ed4c4ec
8 changes: 4 additions & 4 deletions migrate-from-tidb-to-mysql.md
Original file line number Diff line number Diff line change
@@ -56,7 +56,7 @@ After setting up the environment, you can use [Dumpling](/dumpling-overview.md)

1. Disable Garbage Collection (GC).

To ensure that newly written data is not deleted during incremental migration, you should disable GC for the upstream cluster before exporting full data. In this way, history data is not deleted. For TiDB v4.0.0 and later versions, you can skip this step under specific conditions. For more details, see [Manually set the TiDB GC time](/dumpling-overview.md#manually-set-the-tidb-gc-time).
To ensure that newly written data is not deleted during incremental migration, you should disable GC for the upstream cluster before exporting full data. In this way, history data is not deleted. This is a must step since even though Dumpling may [auto-extend the GC](/dumpling-overview.md#manually-set-the-tidb-gc-time) for TiDB v4.0.0 and later versions, after the Dumpling exits, GC may kick in, leading to failure in migrating the incremental change.
Tetsuya3850 marked this conversation as resolved.
Show resolved Hide resolved

Run the following command to disable GC:

@@ -83,7 +83,7 @@ After setting up the environment, you can use [Dumpling](/dumpling-overview.md)
1 row in set (0.00 sec)
```

2. Back up data.
3. Back up data.

1. Export data in SQL format using Dumpling:

@@ -106,7 +106,7 @@ After setting up the environment, you can use [Dumpling](/dumpling-overview.md)
Finished dump at: 2022-06-28 17:49:57
```

3. Restore data.
4. Restore data.

Use MyLoader (an open-source tool) to import data to the downstream MySQL instance. For details about how to install and use MyLoader, see [MyDumpler/MyLoader](https://github.com/mydumper/mydumper). Note that you need to use MyLoader v0.10 or earlier versions. Higher versions cannot process metadata files exported by Dumpling.

@@ -116,7 +116,7 @@ After setting up the environment, you can use [Dumpling](/dumpling-overview.md)
myloader -h 127.0.0.1 -P 3306 -d ./dumpling_output/
```

4. (Optional) Validate data.
5. (Optional) Validate data.

You can use [sync-diff-inspector](/sync-diff-inspector/sync-diff-inspector-overview.md) to check data consistency between upstream and downstream at a certain time.