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 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 subsequent operation (and blocks for minutes), can it potentially > cause all other threads (calling next() on other streams) to block > too? Does something inside the ConsumerConnector block all other > stream processing? This would explain some behaviour we're seeing. > > Thanks, > > Philip >
