-
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
ticdc panic #8216
Labels
affects-6.5
affects-6.6
area/ticdc
Issues or PRs related to TiCDC.
found/automation
Bugs found by automation cases
severity/critical
type/bug
The issue is confirmed as a bug.
Comments
fubinzh
added
area/ticdc
Issues or PRs related to TiCDC.
type/bug
The issue is confirmed as a bug.
labels
Feb 10, 2023
/severity critical |
/found automation |
It's caused by the table sink send resolved ts event to a closed channel. We can fix this problem by disallowing send events after the sink is closed. |
ti-chi-bot
pushed a commit
that referenced
this issue
Feb 10, 2023
This was referenced Feb 10, 2023
ti-chi-bot
added a commit
that referenced
this issue
Feb 10, 2023
ti-chi-bot
added a commit
that referenced
this issue
Feb 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.5
affects-6.6
area/ticdc
Issues or PRs related to TiCDC.
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?
CDC no panic
What did you see instead?
CDC panic
Versions of the cluster
Upstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):Upstream TiKV version (execute
tikv-server --version
):TiCDC version (execute
cdc version
):[2023/02/09 10:46:54.599 +00:00] [INFO] [version.go:47] ["Welcome to Change Data Capture (CDC)"] [release-version=v6.6.0-alpha] [git-hash=0e1322f90b9b72697ca74513c32c0cb64479064c] [git-branch=heads/refs/tags/v6.6.0-alpha] [utc-build-time="2023-02-08 11:41:41"] [go-version="go version go1.19.5 linux/amd64"] [failpoint-build=false]
The text was updated successfully, but these errors were encountered: