-
Notifications
You must be signed in to change notification settings - Fork 287
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-worker may race or panic for invoking query-status and some dmctl command simultaneously #4811
Comments
Root causewe expose the pointer to caller without the lock tiflow/dm/dm/worker/subtask.go Lines 544 to 548 in 3466eaf
should return a copy |
/assign docsir |
@niubell: GitHub didn't allow me to assign the following users: docsir. Note that only pingcap members, 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. |
/unassign niubell |
/assign lyzx2001 |
@niubell: GitHub didn't allow me to assign the following users: lyzx2001. Note that only pingcap members, 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. |
/assign lyzx2001 |
What did you do?
https://ci2.pingcap.net/blue/organizations/jenkins/dm_ghpr_integration_test/detail/dm_ghpr_integration_test/4100/pipeline
What did you expect to see?
no error
What did you see instead?
No response
Versions of the cluster
all version
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: