Re: [DISCUSSION] adding the serializer api back to the new java producer

+1 on this change — APIs are forever. As much as we’d love to see 0.8.2 release ASAP, it is important to get this right. -JW > On Nov 24, 2014, at 5:58 PM, Jun Rao wrote: > > Hi, Everyone, > > I'd like to start a discussion on whether it makes sense to add the > serializer api back to the new

Kafka 0.8.2 profile / hotspot analysis blog post

http://www.autoletics.com/posts/quick-performance-hotspot-analysis-apache-kafka I didn’t do, this, just a pointer to some interesting info, YMMV. -Jonathan

Re: Compile failure going from kafka 0.8.1.1 to 0.8.2

+1 on the two methods suggestion -JW On Oct 30, 2014, at 9:20 AM, Jay Kreps wrote: > But Jun, > > That change breaks peoples code who weren't calling in that way. I don't > think we should be making breaking changes in a point release like this. > > I think we should treat this like a bug for

Re: [DISCUSS] 0.8.1.2 Release

I was one asking for 0.8.1.2 a few weeks back, when 0.8.2 was at least 6-8 weeks out. If we truly believe that 0.8.2 will go “golden” and stable in 2-3 weeks, I, for one, don’t need a 0.8.1.2, but it depends on the confidence in shipping 0.8.2 soonish. YMMV, -Jonathan On Sep 30, 2014, at 12

Re: kafka 0.8.1: Producer.send() can block forever when a broker is down

The issue is that even with one down broker, the rest of the cluster is up, but unreachable from the producer client in this case, which defeats the high availability characteristics of clustering. For any producer trying to use the service, it is "russian roulette" whether you will get meta-d

[DISCUSS] 0.8.2 release branch, "unofficial" release candidates(s), 0.8.1.2 release

+1 on a 0.8.1.2 release as described. I manually applied patches to cobble together a working gradle build for kafka for scala 2.11, but would really appreciate an official release — i.e. 0.8.1.2, as we also have other dependent libraries we use as well (e.g. akka-kafka) that would be much eas