-
Notifications
You must be signed in to change notification settings - Fork 289
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
DM data inconsistency after dm worker down #7658
Labels
affects-5.4
This bug affects the 5.4.x(LTS) versions.
affects-6.1
This bug affects the 6.1.x(LTS) versions.
area/dm
Issues or PRs related to DM.
found/automation
Bugs found by automation cases
severity/critical
type/bug
The issue is confirmed as a bug.
Comments
fubinzh
added
area/dm
Issues or PRs related to DM.
type/bug
The issue is confirmed as a bug.
labels
Nov 21, 2022
dm-master, dm-worker logs |
worker1
master
worker2
|
ref #3737 |
Below error when seen sometimes when running the same test case:
|
/found automation |
/severity critical |
/label affects-5.4 |
/label affects-6.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-5.4
This bug affects the 5.4.x(LTS) versions.
affects-6.1
This bug affects the 6.1.x(LTS) versions.
area/dm
Issues or PRs related to DM.
found/automation
Bugs found by automation cases
severity/critical
type/bug
The issue is confirmed as a bug.
What did you do?
What did you expect to see?
Data should be consistent
What did you see instead?
Data inconsistency seen
Versions of the cluster
DM version (run
dmctl -V
ordm-worker -V
ordm-master -V
):Upstream MySQL/MariaDB server version:
Downstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):How did you deploy DM: tiup or manually?
ti-operator
Other interesting information (system version, hardware config, etc):
current status of DM cluster (execute
query-status <task-name>
in dmctl)The text was updated successfully, but these errors were encountered: