Re: kafka 7 to 8 migration

Hmm, we don't have a built-in tool for the reverse pipeline. However, you can potentially build sth like that yourself using java reflection. Take a look at the implementation of the migration tool. Thanks, Jun On Mon, Mar 17, 2014 at 10:55 AM, Paul Buster wrote: > We were following the docum

Re: queuing support and javadocs (newbie)

We don't have java docs yet. However, you can look at the client api at http://kafka.apache.org/documentation.html#api The queue (or the buffer) in the producer client is in-memory only. If network connection is down, you can keep retrying sending the messages in the buffer. However, the buffer is

Re: 0.8.1 stability

+1 -Jay On Tue, Mar 18, 2014 at 5:56 PM, Neha Narkhede wrote: > Thanks for giving the 0.8.1 release a spin! A few people have reported bugs > with delete topic and > also the automatic leader > rebalancing

Re: 0.8.1 stability

I am +1 on a 0.8.1.1 release ( off the 0.8.1 branch tagged) for blocking bug fixes. If we have features/improvements for 0.8.2 then we should hold them off ( with 0.9.0 providing more system changes). /*** Joe Stein Founder, Principal Consultant Big D

Re: 0.8.1 stability

Hi, We are in the process of migrating to 0.8.1, so we haven't seen any bugs yet, but would welcome a bugfix release if others are reporting issues. Versioning Q: wouldn't that be 0.8.2? Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://semate

Re: 0.8.1 stability

A point release focusing on stability would definitely be nice. And maybe a table in a wiki marking the stability of various features (core, replication, synchronous messageing, compaction, rebalancing, topic create, etc), so that people don't end up in the danger zone on prod deployments. - Niek

Re: 0.8.1 stability

Auto rebalance is already turned off in 0.8.1. On 3/18/14 5:56 PM, "Neha Narkhede" wrote: >Thanks for giving the 0.8.1 release a spin! A few people have reported >bugs >with delete topic and >also the automatic leader >rebalancing

0.8.1 stability

Thanks for giving the 0.8.1 release a spin! A few people have reported bugs with delete topic and also the automatic leader rebalancingfeature that we released as part of 0.8.1. These features were

Re: Impact of slow consumers

In general this is expected. Consumers generally read from the OS cache and so they do no I/O. However a slow consumer may fall out of this cached portion of the log and do real reads. These reads will compete with writes for disk bandwidth. However what is puzzling is that you mention that other

Re: Impact of slow consumers

Hi Guozhang, The throughput refers to the broker side throughput. The peak time throughput of broker for the topic is around (9-10 MBps) but with slow consumers the throughput went down to 5-6 MBps. I consume data using a consumer group. Consumer group needs 5 consumers to consume the entire data

Re: Impact of slow consumers

Hello Abhinav, When you say "slow consumer set on topic1", do you mean you have a consumer group consuming from topic1, with one of them slow, or do you mean all consumers are slow in that group, or do you use a simple consumer? When you say "throughput", do you mean consumer side throughput, or b

Impact of slow consumers

I was testing the impact of slow consumers on Kafka. I had slow consumers set on topic1. The throughput of topic1 went down by 40-50% for the peak period (~ 9-10 MBps). Though the throughput for other topics was not affected at all. I couldn't find any error logs on the server side or producer. Th

kafka 7 to 8 migration

We were following the documented upgrade path - using the migration tool, updating consumers to 8, then planing to produce to 8 when the consumers are all ported. But, we’ve run into logistical issues. We have a storm topology (java) where we’d like to consume from a kafka 8 cluster and produce