Follower brokers not syncing with 0.8.2
Hello folks We have currently have a cluster of 20 nodes running Kafka 0.8.1.1 serving a large volume of production traffic. I'm bringing up another 20 nodes with Kafka 0.8.2.0 in the same cluster, currently serving a test topic with 32 partitions spread across the 20 new nodes, with replication factor 2. I had a leader and an in-sync replica for all partitions. I recently restarted the new nodes. After the restart, all the partitions of the test topic still have leaders, but only 2 out of 32 partitions have ISRs. I enabled debug logging for one of the brokers that wasn't syncing, but there doesn't seem to be anything useful in there. It doesn't seem to be fetching from the leader at all. I stopped it again and deleted its data directory completely and restarted, but still no luck. Anybody seen this before? Anything in the log that I can provide to debug further? Regards Albert
Re: dumping JMX data
On Fri, Jan 16, 2015 at 5:52 PM, Joe Stein joe.st...@stealth.ly wrote: Here are some more tools for that https://cwiki.apache.org/confluence/display/KAFKA/JMX+Reporters depending on what you have in place and what you are trying todo different options exist. A lot of folks like JMX Trans. We tried JMX Trans for a while, but didn't like it very much. Jolokia looks promising. Trying that now. http://www.jolokia.org/
Production settings for JDK 7 + G1 GC
Greetings all We're expanding our Kafka cluster, and I thought this would be a good time to try the suggestions in http://www.slideshare.net/ToddPalino/enterprise-kafka-kafka-as-a-service slide #37 about running on JDK 7 with G1 GC. Anybody (Todd?) that could shed some light on a complete set of good GC flags to start with and what the best JDK version is to run with these days? Thanks! Regards Albert
