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

Upgrade Clickhouse to 23.8 #3001

Closed
hubertdeng123 opened this issue Apr 26, 2024 · 5 comments
Closed

Upgrade Clickhouse to 23.8 #3001

hubertdeng123 opened this issue Apr 26, 2024 · 5 comments

Comments

@hubertdeng123
Copy link
Member

hubertdeng123 commented Apr 26, 2024

Prod is being upgraded, so we should also do this for self-hosted users.

Looks like 21.8 -> 22.8 -> 23.3 -> 23.8

Although, perhaps it is possible to go from 22.8 -> 23.8 because self-hosted upgrades will always incur downtime.

https://docs.altinity.com/releasenotes/altinity-stable-release-notes/23.8/#major-changes-that-require-attention

We should also look to automate this process or make it easier for devs to verify clickhouse upgrades for self-hosted.

@williamdes
Copy link
Contributor

By coincidence I upgraded to 23.8.8.21.altinitystable

apt install clickhouse-server=22.8.20.12.altinitystable clickhouse-common-static=22.8.20.12.altinitystable
apt install clickhouse-server=23.8.8.21.altinitystable clickhouse-common-static=23.8.8.21.altinitystable

But

<!-- This include is important!
It is required for the version of Clickhouse
used on ARM to read the environment variable. -->
<include from_env="MAX_MEMORY_USAGE_RATIO"/>

Will break Clickhouse. You need to use (default value for example)

<max_server_memory_usage_to_ram_ratio>0.9</max_server_memory_usage_to_ram_ratio>

@hubertdeng123
Copy link
Member Author

@williamdes I was able to get past the error by removing the newlines 🤔

@williamdes
Copy link
Contributor

@williamdes I was able to get past the error by removing the newlines 🤔

Okay, well I did not want to fight more as it was a nightmare finding this block. Great that the env can be kept as is

@dlouzan
Copy link

dlouzan commented May 23, 2024

We run a self-hosted setup in which we cannot rely on the provided scripts for migrations, so we need to rewrite them for our configuration, and while migrating to 24.5.0 I was just confronted with this issue, it definitely didn't cross my mind that breaking the xml into multiple lines for readibility would kill clickhouse 😅

Perhaps a short comment on

<max_server_memory_usage_to_ram_ratio><include from_env="MAX_MEMORY_USAGE_RATIO"/></max_server_memory_usage_to_ram_ratio>
referencing the upstream issue will help others in the future.

@hubertdeng123
Copy link
Member Author

@dlouzan I've added this in #3085. Closing this issue as this has been completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Archived in project
Archived in project
Development

No branches or pull requests

4 participants