-
Notifications
You must be signed in to change notification settings - Fork 286
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 print many log caused by "COMMIT" in binlog query event #7525
Comments
since we assume all "commit" event is XIDEvent, the missing handling of "COMMIT" query event will cause some bug
|
/cc @GMHDBJD |
/assign @liumengya94 |
@lance6716: GitHub didn't allow me to assign the following users: liumengya94. Note that only pingcap members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What did you do?
https://asktug.com/t/topic/995146/9
though we have no clue how it happens, we should skip printing it
What did you expect to see?
No response
What did you see instead?
No response
Versions of the cluster
DM version (run
dmctl -V
ordm-worker -V
ordm-master -V
):all version
Upstream MySQL/MariaDB server version:
5.7
current status of DM cluster (execute
query-status <task-name>
in dmctl)(paste current status of DM cluster here)
The text was updated successfully, but these errors were encountered: