[
https://issues.apache.org/jira/browse/KAFKA-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099874#comment-14099874
]
Gwen Shapira commented on KAFKA-1485:
-------------------------------------
Hi Jun,
I'm still waiting to hear from my ZooKeeper colleagues about 3.4.7 plans.
>From what I understand, Kafka deployments don't necessarily use the ZooKeeper
>server packaged with Kafka. As such, the dependency we choose is for the
>client - and there hasn't been too many client changes between 3.4.5 and 3.4.6.
We decided to go with 3.4.6 since Todd mentioned that LinkedIn will be using
3.4.6 and its good to match the version of the largest production deployment :)
That said, Cloudera is still shipping 3.4.5 (plus few patches), most of our
customers run Kafka with 3.4.5. I don't see issues going with 3.4.5.
TL;DR;
3.4.5 is very stable. 3.4.6 seems to be the LinkedIn version. Both are great
choices and I don't care which way we go. But please lets not release another
3.3.X version...
> Upgrade to Zookeeper 3.4.6 and create "shim" for ZKCLI so system tests can run
> ------------------------------------------------------------------------------
>
> Key: KAFKA-1485
> URL: https://issues.apache.org/jira/browse/KAFKA-1485
> Project: Kafka
> Issue Type: Wish
> Affects Versions: 0.8.1.1
> Reporter: Machiel Groeneveld
> Assignee: Gwen Shapira
> Labels: newbie
> Fix For: 0.8.2
>
> Attachments: KAFKA-1485.2.patch, KAFKA-1485.3.patch, KAFKA-1485.patch
>
>
> I can't run projects alongside Kafka that use zookeeper 3.4 jars. 3.4 has
> been out for 2.5 years and seems to be ready for adoption.
> In particular Apache Storm will upgrade to Zookeeper 3.4.x in their next
> 0.9.2 release. I can't run both versions in my tests at the same time.
> The only compile problem I saw was in EmbeddedZookeeper.scala
--
This message was sent by Atlassian JIRA
(v6.2#6252)
