That could be a bug, but I don't recall any zkconsumerconnector fixes since 0.6. Can you check if the consumer is actually registered in zk at the time? It should be present in /consumers/<your consumer group>/ids
On Wed, Oct 12, 2011 at 10:52 AM, Mathias Herberts <mathias.herbe...@gmail.com> wrote: >> If that error occurs when the broker is down, this is normal. When the >> broker is brought up again, a rebalance will be triggered in the consumers >> and a new fetcher to the restarted broker should be established. Could you >> check if there is any rebalance after that error (search for "rebalancing") >> and whether new fetchers are started afterwards? Also, what version of Kafka >> are you using? > > Hi, > > the version of Kafka we are using is 0.6, what surprised me was the > fact that there was no rebalancing once the Kafka node came back up. > > Could it be a ZK issue with a missed watch? > > Mathias. >
