-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Some old tables that never get garbage collected #61188
Comments
Hello, I am Blathers. I am here to help you get the issue triaged. Hoot - a bug! Though bugs are the bane of my existence, rest assured the wretched thing will get the best of care here. I have CC'd a few people who may be able to assist you:
If we have not gotten back to your issue within a few business days, you can try the following:
🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan. |
If this is the same cluster as those, I'm not totally surprised to hear that we've got some cleanup to do. Please share the debug zip with |
I shared the file with gdrive. |
One question: how willing are you to upgrade to 20.2? We have added tools in 20.2 to make repair much more robust and much simpler - it can be done in sql without the need for some low level hacks. It's possible in 20.1, but certainly less pleasant. |
That sounds great. |
Cool, I'll cook something up. Out of curiosity, does SHOW TABLES work or does it currently give you an error? |
SHOW TABLES works on all databases SHOW DATABASES shows. |
We added functions to remove these tables and their data with |
Great news, thank you very much! |
Describe the problem
I have some old tables that never gets garbage collected.
This doesn’t seem to be a real problem as everything works wonderfully and I have never experienced such a problem since then. Nevertheless, I would like to remove them if it is possible.
Also see: https://forum.cockroachlabs.com/t/some-old-tables-that-never-get-garbage-collected/4302
To Reproduce
I don't know because it only happened once.
I already had some consinstency problems at that time:
#51983, #52422
possibly it is related to one of these problems.
Expected behavior
The tables should be garbage collected and dissapear.
Additional data / screenshots
I've already created the debug.zip.
What is the preferred way to transfer it privately?
Jira issue: CRDB-3053
The text was updated successfully, but these errors were encountered: