Skip to content
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

schema storage consumes too much memory after schemas should have been GC'd #3174

Closed
liuzix opened this issue Oct 29, 2021 · 0 comments · Fixed by #3172
Closed

schema storage consumes too much memory after schemas should have been GC'd #3174

liuzix opened this issue Oct 29, 2021 · 0 comments · Fixed by #3172
Assignees
Labels
affects-4.0 affects-5.1 area/ticdc Issues or PRs related to TiCDC. severity/major type/bug The issue is confirmed as a bug.

Comments

@liuzix
Copy link
Contributor

liuzix commented Oct 29, 2021

What did you do?

Executes 30000 Truncate DDLs on about 300 tables, all of which are NOT within the filter of TiCDC.

What did you expect to see?

After checkpoint catches up, the memory consumption should fall back to the baseline.

What did you see instead?

Screenshot from 2021-10-29 11-39-12

profile001

Memory consumption does not fall back on all TiCDC nodes.

Versions of the cluster

v5.1.2 (likely to exist on all versions)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.0 affects-5.1 area/ticdc Issues or PRs related to TiCDC. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants