-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Upgrade Clickhouse to 21.8 #2536
Conversation
can you explain the |
Sure, |
tested in dev, it's working for me |
Should we be using the |
Don't think there is much of a difference there as I couldn't find much online. It's newer and the version of clickhouse used is more close to the .testingarm version. Seems fine to use and I've tested it locally |
@nikhars Do you know which we should be using here? It was my understanding that the testing versions are generally more stable than the dev ones but I couldn't find details about it online. |
Does anyone has a reference of why the name changes that would help me trust the new image rather than the Yandex namespace? |
The Altinity versions are maintained for 3 years, we use Altinity builds in Sentry's production clusters so that we can have more stability when it comes to upgrading our clusters. According to their docs, they are 100% compatible with the community builds: https://docs.altinity.com/altinitystablebuilds/ cc @williamdes |
Thank you! |
Hi @hubertdeng123 should this fix the issue with Replays and Clickhouse mentioned by @cmanallen in getsentry/sentry#57326 (comment) ? |
@Cybernisk Yes, this should fix the issue that you have. |
Upgrades clickhouse for self-hosted users. Tested it out on our own self-hosted Sentry instance and it seems to work smoothly 🤞