Re: One 0.72 ConsumerConnector, multiple threads, 1 blocks. What happens?
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.
On Wed, Jun 12, 2013 at 9:10 PM, Philip O'Toole <[EMAIL PROTECTED]> wrote: