Jun - thanks again. This is very helpful.
Philip
On Jun 12, 2013, at 9:50 PM, Jun Rao jun...@gmail.com wrote:
Actually, you are right. This can happen on a single topic too, if you have
more than one consumer thread. Each consumer thread pulls data from a
blocking queue, one or more
Hello -- we're using 0.72. We're looking at the source, but want to be sure. :-)
We create a single ConsumerConnector, call createMessageStreams, and
hand the streams off to individual threads. If one of those threads
calls next() on a stream, gets some messages, and then *blocks* in
some
Yes, when the consumer is consuming multiple topics, if one thread stops
consuming topic 1, it can prevent new data getting into the consumer for
topic 2.
Thanks,
Jun
On Wed, Jun 12, 2013 at 7:43 PM, Philip O'Toole phi...@loggly.com wrote:
Hello -- we're using 0.72. We're looking at the
Jun -- thanks.
But if the topic is the same, doesn't each thread get a partition?
Isn't that how it works?
Philip
On Wed, Jun 12, 2013 at 9:08 PM, Jun Rao jun...@gmail.com wrote:
Yes, when the consumer is consuming multiple topics, if one thread stops
consuming topic 1, it can prevent new
Also, what is it in the ConsumerConnection that causes this behaviour?
I'm proposing here that we move to a model of ConsumerConnection per
thread. This will decouple the flow for each partition, and allow each
to flow, right? We only have one topic on the cluster.
Thanks,
Philip
On Wed, Jun
