-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Record new_collation setting in br backup and compare new_collation during restore #33422
Closed
fubinzh opened this issue
Mar 25, 2022
· 3 comments
· Fixed by #33500 or pingcap/kvproto#887 · May be fixed by #33593
Closed
Record new_collation setting in br backup and compare new_collation during restore #33422
fubinzh opened this issue
Mar 25, 2022
· 3 comments
· Fixed by #33500 or pingcap/kvproto#887 · May be fixed by #33593
Labels
affects-5.2
This bug affects 5.2.x versions.
affects-5.3
This bug affects 5.3.x versions.
affects-5.4
This bug affects 5.4.x versions.
affects-6.0
component/br
This issue is related to BR of TiDB.
severity/major
type/bug
This issue is a bug.
Comments
fubinzh
added
type/bug
This issue is a bug.
severity/major
component/br
This issue is related to BR of TiDB.
labels
Mar 25, 2022
ti-chi-bot
added
may-affects-4.0
This bug maybe affects 4.0.x versions.
may-affects-5.0
This bug maybe affects 5.0.x versions.
may-affects-5.1
This bug maybe affects 5.1.x versions.
may-affects-5.2
This bug maybe affects 5.2.x versions.
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.0
labels
Mar 25, 2022
3pointer
added
affects-5.4
This bug affects 5.4.x versions.
and removed
may-affects-4.0
This bug maybe affects 4.0.x versions.
may-affects-5.1
This bug maybe affects 5.1.x versions.
may-affects-5.2
This bug maybe affects 5.2.x versions.
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-5.0
This bug maybe affects 5.0.x versions.
labels
Mar 28, 2022
12 tasks
ti-chi-bot
pushed a commit
that referenced
this issue
Mar 28, 2022
This was referenced Mar 29, 2022
12 tasks
This was referenced Apr 13, 2022
/affects-5.2 |
/label affects-5.2 |
/label affects-5.3 |
ti-chi-bot
pushed a commit
that referenced
this issue
Apr 28, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Jun 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-5.2
This bug affects 5.2.x versions.
affects-5.3
This bug affects 5.3.x versions.
affects-5.4
This bug affects 5.4.x versions.
affects-6.0
component/br
This issue is related to BR of TiDB.
severity/major
type/bug
This issue is a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
To archive this, we need to:
a. During br backup, we can record new_collation setting of the tidb cluster.
b. When we restore to a target cluster, br can compare new_collation setting of the target cluster with that in the backup, and prevent user from restore if they are not the same.
3. What did you see instead (Required)
Currently br restored data may have checksum and index error if source tidb and target tidb has different new_collation settings, and we reply on user to make sure they are the same, which is not user friendly.
4. What is your TiDB version? (Required)
BR 6.0.0
The text was updated successfully, but these errors were encountered: