3 ms·
Util one day ZK fails in the most spectacular way and nobody knows the internals of it and you lose data. Just because is something fine for a time does not mea
by StreamBright 8y ago
Util one day ZK fails in the most spectacular way and nobody knows the internals of it and you lose data. Just because is something fine for a time does not mean that it is reliable. Without telling us how many nodes you are running ZK/Kafka on this information is useless.
Others were not so lucky:
https://issues.apache.org/jira/browse/ZOOKEEPER-801 https://issues.apache.org/jira/browse/ZOOKEEPER-801
- neeleshs 8y agoI'm not claiming it's perfect. Our cluster of > 15 Kafka nodes and 3 node zk ensemble has had no major issues in over 4 years in production. That's something. And from the bug - "GC logging/tuning is clearly where I dropped the ball, just using the defaults;"