-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Clickhouse corrupt after server failure #2832
Comments
Assigning to @getsentry/support for routing ⏲️ |
|
Routing to @getsentry/product-owners-settings-integrations for triage ⏲️ |
You may need to manually remove rows from your clickhouse table since it looks like corrupt data got in. |
Hey thanks for the response. Nobody in our company has worked with clickhouse before. So we don't know how the database functions or we can connect to it. Do we just drop files somewhere? We don't really care about the existing replays and are wondering if there is a way to simply wipe the table so it recreates it. We just want the selfhosted sentry up and running. |
I believe you should be able to drop the table |
Hey, if i remove the volume for clickhouse and postgres then i imagine that i will lose a lot more then just the replays. Are all my configurations inside sentry and my user accounts then also gone? |
I have a similar problem, in my case the VPS ran out of space and I caused a clickhouse error (I think when saving). Now clickhouse won't start, try deleting the volume to see if it migrates back but nothing seems to happen.
And after delete the volume and try to upgrade:
thanks |
I just solved it by increasing the total of "max_suspicious_broken_parts" in the clickhouse configuration, by default they are 10/100 and I increased it to 1000. Keep in mind that the parts that give errors will be omitted and you will not be able to recover them. You can add this to your configuration.
References: |
Thanks for throwing up that PR! I've left a comment, but it looks like a good thing to add. |
After raising the limit my sentry's clickhous DB also starts. Thanks. |
Environment
self-hosted (https://develop.sentry.dev/self-hosted/)
What are you trying to accomplish?
Hi,
The server that our self hosted sentry runt on had a hardware failure causing it to shutdown. After getting everything back up and running sentry no longer starts up.
Running docker compose up -d i get the following output:
I tried reinstalling using ./install.sh and after that i tried updating it to the latest version but i again get this output:
How are you getting stuck?
Because of this sentry isn't starting. It seems that the clickhouse DB is corrupted, can i just drop the files of it and will it recover? I am guessing that issues are stored in it.
Maybe there is a command to try a self-repair?
Oh and BTW:
this says that the latest version is 24.3.0 while it is 24.2.0
https://develop.sentry.dev/self-hosted/releases/
Where in the product are you?
Other
Link
No response
DSN
No response
Version
24.2.0
The text was updated successfully, but these errors were encountered: