-
Notifications
You must be signed in to change notification settings - Fork 288
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 panic when import data via lightning physical backend #8209
Labels
affects-6.6
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
Feb 9, 2023
fubinzh
changed the title
DM panic
DM panic when import data via lightning physical backend
Feb 9, 2023
/severity Critical |
seems it's a bug at lightning side, will try to reproduce it |
ti-chi-bot
pushed a commit
that referenced
this issue
Feb 10, 2023
lance6716
added a commit
to lance6716/ticdc
that referenced
this issue
Feb 10, 2023
ti-chi-bot
pushed a commit
that referenced
this issue
Feb 10, 2023
/found automation |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.6
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?
What did you see instead?
panic seen
2023-02-08 19:42:37 | {"pod":"dm-dm-worker-0","container":"dm-worker","log":"2023-02-08T19:42:37.551472559+08:00 stderr F panic: send on closed channel","namespace":"dm-lighting-physical-backend-big-tps-1560715-1-410"}
Versions of the cluster
[2023/02/08 10:48:35.168 +00:00] [INFO] [version.go:47] ["Welcome to dm-worker"] [release-version=v6.6.0-alpha] [git-hash=c
aa73987b7a3f08e701e45190ad5c10bade542b9] [git-branch=heads/refs/tags/v6.6.0-alpha] [utc-build-time="2023-02-07 11:42:54"] [go-version="go version go1.19.5 linux/amd64"] [failpoint-build=false]
current status of DM cluster (execute
query-status <task-name>
in dmctl)The text was updated successfully, but these errors were encountered: