kafka metrics emitting to graphite

How to configure, to emit kafka broker metrics to graphite. t SunilKalva

Re: Is kafka 8 and LeaderNotAvailableError

Its working great now. Thanks On Sat, Oct 10, 2015 at 3:35 AM, Prabhjot Bharaj wrote: > Zoo.cfg looks OK to me > > Please post your reply whether it worked after changing those values > > If not, we'll figure out something > > Also, I forgot to tell earlier, please

Re: kafka metrics emitting to graphite

Hi Sunil Try using JMXTrans to expose Kafka’s internal JMX metrics to graphite. https://github.com/jmxtrans/jmxtrans B > On 11 Oct 2015, at 11:19, sunil kalva wrote: > > How to configure, to emit kafka broker metrics to graphite.

Better API/Javadocs?

Will Kafka v0.9 publish official javadocs for the entire API? In 0.8, javadocs appear rather sparse. It's hard to find a javadoc that documents both Consumers and Producers. Also, will future versions of Kafka have more intuitive serializer/deserializer interfaces? E.g., if a Producer can

Re: Is kafka 8 and LeaderNotAvailableError

Wow. Nice. So, what all did you change in your cluster?? Regards, Prabhjot On Oct 11, 2015 7:58 PM, "David Montgomery" wrote: > Its working great now. Thanks > > On Sat, Oct 10, 2015 at 3:35 AM, Prabhjot Bharaj > wrote: > > > Zoo.cfg looks

Re: Kafka availability guarantee

To answer the question, yes, it is incorrect. There are a few things you can do to minimize problems. One is to disable unclean leader election, use acks=-1 on the producers, have an RF of 3 or greater, and set the min ISR to 2. This means that the topic will only be available if there are at

Re: Kafka availability guarantee

On Sun, Oct 11, 2015 at 2:34 PM, Todd Palino wrote: > To answer the question, yes, it is incorrect. There are a few things you > can do to minimize problems. One is to disable unclean leader election, use > acks=-1 on the producers, have an RF of 3 or greater, and set the min

Re: Better API/Javadocs?

On Javadocs, both new clients (producer and consumer) have very thorough documentation in the javadocs. 0.9.0.0 will be the first release with the new consumer. On deserialization, the new consumer lets you specify deserializers just like you do for the new producer. But the old consumer supports

Kafka availability guarantee

Reading through the Kafka documentation for statements regarding Kafka's availability guarantees one comes across this statement: *With this ISR model and f+1 replicas, a Kafka topic can tolerate f failures without losing committed messages.* In my opinion, this appears incorrect or at best