Update from our OPS team, regarding zookeeper 3.4.x. Given stability, adoption of offset batching would be the only remaining bit of work to do. Still, I totally understand the restraint for 0.8... "As exercise in upgradability of zookeeper, I did a "out-of-the"box" upgrade on Zookeeper. I downloaded a generic distribution of Apache Zookeeper and used it for the upgrade.
Kafka included version of Zookeeper 3.3.3. Out of the box Apache Zookeeper 3.4.5 (which I upgraded to)
Running, working great. I did *not* have to wipe out the zookeeper databases. All data stayed intact.
I got a new feature, which allows auto-purging of logs. This keeps OPS maintenance to a minimum." thanks, rob
There is no particular need for storing the offsets in zookeeper. In fact with Kafka 0.8, since partitions will be highly available, offsets could be stored in Kafka topics. However, we haven't ironed out the design for this yet.
Thanks, Neha On Fri, May 17, 2013 at 2:19 PM, Scott Clasen <[EMAIL PROTECTED]> wrote:
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext