-
Notifications
You must be signed in to change notification settings - Fork 74
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
proton requires GLIBC_2.27 to run #871
Comments
Hi @toddyocum , thanks for reporting this issue. We will look into it. In the meanwhile, is docker container an option to unblock you first ? |
Hi @chenziliang , docker isn't an option on our embedded linux (I wish it was) But not a big deal, the PoC is a low priority atm. We are heavy users of ClickHouse and (lots of) MV's, and was curious to see what proton might offer over what we use. |
thanks, I can reproduce it with ubuntu1604
|
Hi @toddyocum, thanks for the updates. Proton adds other functionalities like native JavaScript UDA and UDF, incremental join, incremental aggregation, incremental data deduplication, as well as streaming windows like hopping, sessionization, and high concurrent data ingest with small batches etc functions which are all complementary use cases to ClickHouse. We have quite a few users who deployed a Proton tier in front of ClickHouse doing ETL, streaming enchantments as well as light join, aggression and handle concurrent ingest before sending the data to ClickHouse. For this glibc issue specifically, as the corresponding PR indicates, it is the embedded JavaScript V8 engine which depends on higher glibc version. We can disable the JavaScript and provide a binary for you to experiment. Thanks! |
hi @toddyocum, thank you for reporting this issue. |
Describe what's wrong
Unable to run proton-v1.6.3-Linux-x86_64 because of missing glibc requirement
How to reproduce
Try to run proton:
Our embedded linux ( a customized older Fedora install ) libc version
Error message and/or stacktrace
Additional context
ClickHouse on the same box works, so was surprised that proton, which is built on top of/forked from ClickHouse, has a different run-time requirement.
So might not be a bug, just a different requirement, but leaves us without a path forward at this time for trying out proton.
The text was updated successfully, but these errors were encountered: