Hello, Team, As per this, zookeeper is not necessary for single node clickhouse and I do not think there's an option to not use a zookeeper in the SigNoz/ClickHouse helm chart. Any help on how to disable it and whether we even should (to save on memory) ?
s
Srikanth Chekuri
07/10/2024, 8:26 AM
It's a very lightweight container. You do not gain much by removing it.
a
Ayush Rathore
07/10/2024, 8:29 AM
@Srikanth Chekuri Agreed, but we have a use case where we have to reduce the entire stack within 2 GB of RAM, while we already managed to bring it down to 2.9 GB, releasing around 300 MBs used by zookeeper would help us a long way in that, Any way to do that?
Thanks for your reply 👍
Ayush Rathore
07/10/2024, 11:00 AM
After removing ZooKeeper fom the ClickHouseInstallation CRD, Only the schema-migrator is failing, but the cluster other wise is running fine, Could @Srikanth Chekuri or anyone else give a hint about why the schema migrator needs zookeeper to run or refer me to a related doc, I am looking to make it work.
s
Srikanth Chekuri
07/10/2024, 12:41 PM
There would errors in ClickHouse without zookeeper
a
Ayush Rathore
07/10/2024, 1:50 PM
@Srikanth Chekuri
Yes, but it is only failing when clickhouse is initialised in the absence of zookeeper, Once it starts, scaling zookeeper down does not make any difference, am adding a post install hook to scale zookeeper down after clickhouse is up. This approach would impair clickhouse in case of a automatic restart, but this seems to be the only way to go to save that 300MB. Any better ideas or suggestions are welcome.
SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.