4 ms·
Not to be a the stick in the mud here. We recently moved from Clickhouse to Druid due to issues we were having when scaling and rebalancing the cluster. How doe
by tobykeef 5y ago
Not to be a the stick in the mud here. We recently moved from Clickhouse to Druid due to issues we were having when scaling and rebalancing the cluster. How does removing ZK help?
- dreyfan 5y agoBecause ZK is garbage and complicates every clustered application that relies on it? Kafka is ditching ZK too. Clickhouse cluster quite simply doesn’t support elastic rebalancing. Avoid CH if that is a hard requirement for your setup.
- StreamBright 5y agoI used to have a wipe this ZK node clean and rejoin the cluster script to deal with ZK node outages that nobody could explain.
- log4shell 5y agoDruid has quite some intelligence baked in to handle the scaling by default. I am curious how clickhouse is doing in all those aspects. When we did a PoC, the operational aspect of clickhouse and performance was severely lacking as compared to druid. Clickhouse had bigger resources at its disposal than druid during this PoC. If they could improve the operational aspect and introduce sensible defaults so that the users don't have to go through 10000 configuration to work with data in clickhouse, I am sure I will give it a go for some other usecase. It is simple on surface but devil is in the details. Druid is much simpler and sane at the scale I need to operate.
- benjaminwootton 5y agoInteresting. We moved from Druid to Clickhouse for exactly the same reason :-) https://timeflow.systems/why-we-moved-from-druid-to-clickhouse https://timeflow.systems/why-we-moved-from-druid-to-clickhou... Clickhouse is significantly easier to operate than Druid in my experience.