Added a patch.
On Mon, Aug 4, 2014 at 7:25 PM, Joe Stein <joe.st...@stealth.ly> wrote: > I found an already open ticket in regards to this > https://issues.apache.org/jira/browse/KAFKA-1485 > > It also references a conflict with storm upgrading and testing and some > other conflicts too. > > /******************************************* > Joe Stein > Founder, Principal Consultant > Big Data Open Source Security LLC > http://www.stealth.ly > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > ********************************************/ > > > On Mon, Aug 4, 2014 at 9:57 PM, Joe Stein <joe.st...@stealth.ly> wrote: > >> Thanks Todd, very good to know and learn! >> >> - Joestein >> >> >> On Mon, Aug 4, 2014 at 9:44 PM, Todd Palino <tpal...@linkedin.com.invalid> >> wrote: >> >>> We¹ve started running our test cluster against a Zookeeper 3.4.6 ensemble. >>> So far, we¹ve had no problems with it that were specific to ZK (since >>> we¹re using it for testing trunk version of Kafka, as well as mirror >>> maker, we have plenty of problems with it. Just none that are ZK). We¹re >>> probably going to start rolling that out to our Kafka clusters in the >>> staging environments in the next month or so. That¹s a bigger step, since >>> we treat those clusters more like production (they¹re staging for everyone >>> else, but we¹re infrastructure). >>> >>> -Todd >>> >>> >>> On 8/3/14, 9:56 PM, "Gwen Shapira" <gshap...@cloudera.com> wrote: >>> >>> >Hi, >>> > >>> >Kafka currently builds against Zookeeper 3.3.4, which is quite old. >>> > >>> >Perhaps we should move to the more recent 3.4.x branch? >>> > >>> >I tested the change on my system and the only impact is to >>> >EmbeddedZookeeper used in tests (it uses NIOServerCnxn.factory, which >>> >was refactored into its own class in 3.4). >>> > >>> >Here's what the change looks like: >>> >https://gist.github.com/gwenshap/d95b36e0bced53cab5bb >>> > >>> >Gwen >>> >>> >>
