11–20 of 21 posts
Off-topic, but does Zookeeper have features that etcd doesn't provide? etcd seems to be simpler to operate at a glance.
Off-topic, but does Zookeeper have features that etcd doesn't provide? etcd seems to be simpler to operate at a glance.
Otherwise manually managing it is crufty and ancient feeling. The API for “dynamic reconfiguration” is like something I’d expect from Oracle software in the 90s. It sucks.
Off-topic, but does Zookeeper have features that etcd doesn't provide? etcd seems to be simpler to operate at a glance.
Not much they have pretty compatible feature overlap. Zookeeper pushes pretty heavily on a smart client rather than handling a lot of stuff server side. If I were to pick I'd go with etcd in a heartbeat. Every con they list on their comparison website is stuff I've personally dealt with in ZK. https://etcd.io/docs/v3.3/learning/why/#zookeeper
Then why there are so many projects still rely on Zookeeper and spend so much time on re-writing its features instead of switching to etcd like what OP, ClickHouse (in the discussion), and Kafka (KRaft) are doing? It there something that etcd won't fit?
Earlier quoted context omitted.
Not much they have pretty compatible feature overlap. Zookeeper pushes pretty heavily on a smart client rather than handling a lot of stuff server side. If I were to pick I'd go with etcd in a heartbeat. Every con they list on their comparison website is stuff I've personally dealt with in ZK. https://etcd.io/docs/v3.3/learning/why/#zookeeper
Actually I was asking the question looking at the etcd doc you linked. The etcd doc explains like it is just better than Zookeeper. Then why there are so many projects still rely on Zookeeper and spend so much time on re-writing its features instead of switching to etcd like what OP, ClickHouse (in the discussion), and Kafka (KRaft) are doing? It there something that etcd won't fit?
There's a good talk by ClickHouse committer Alexander Sapin that explains the design considerations: https://www.youtube.com/watch?v=abhcCRW09Ac
Quoted post unavailable.
Quoted post unavailable.
Quoted post unavailable.
Earlier quoted context omitted.
Not much they have pretty compatible feature overlap. Zookeeper pushes pretty heavily on a smart client rather than handling a lot of stuff server side. If I were to pick I'd go with etcd in a heartbeat. Every con they list on their comparison website is stuff I've personally dealt with in ZK. https://etcd.io/docs/v3.3/learning/why/#zookeeper
Actually I was asking the question looking at the etcd doc you linked. The etcd doc explains like it is just better than Zookeeper. Then why there are so many projects still rely on Zookeeper and spend so much time on re-writing its features instead of switching to etcd like what OP, ClickHouse (in the discussion), and Kafka (KRaft) are doing? It there something that etcd won't fit?
Curious when the folks at ClickHouse are going to decide to spin its custom rewrite of ZooKeeper in C++ (ClickHouse-Keeper [1]) out into its own separate project. [1] https://clickhouse.com/docs/en/operations/clickhouse-keeper/
(I'm not a committer but have a lively interest in the topic as my company supports a couple hundred customers running on ClickHouse.)