Hi Guozhang,
sorry for asking a little unrelated problem here.
We found a consumer stopping fetching data when doing an network upgrade,
if the consumer have connection problem with one broker (but OK with
zookeeper and other brokers)
the fetcherrunnable will stop, but there is no chance to resta
Hi Yonghui,
Could you check if consumer2's fetcher thread is still alive? Also we have
an entry in FAQ wiki page about "consumer stopped consuming", current
Apache has some issues with the wiki page, but you may want to check it out
once Apache page resumes.
Guozhang
On Wed, May 14, 2014 at 8:5
Thanks GuoZhang.
After last accident, we stop all consumers and then restart all consumers
one by one then it is ok.
2 brokers, 10 partitions / broker, 3 consumers, each create 10 stream
So consumer1 consumes 10 partitions, consumer2 consumers another 10
partitions, consumer3 is idle.
Tod
Hello Yonghui,
In 0.7 the consumer rebalance logic is distributed and in some corner cases
such as soft-failure-caused-consecutive rebalances some consumer may
consider the rebalance as complete while others are still trying the
rebalance process. You can check the GC logs on your consumer to veri
