The closed by interrupt exception is because the underlying
"leader-finder-thread" has been interrupted - this is done for e.g.,
on a rebalance. Do you see any rebalancing messages in your consumer
logs? How many topics are you consuming? Are the topics present on the
broker and is there a leader for each of them (i.e., without any
leader movement)? Can you try running a console consumer to see if you
see the same behavior?


On Mon, Aug 12, 2013 at 10:27 AM, Eric Sites <[EMAIL PROTECTED]> wrote:

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB