-Re: Kafka 0.8's ConsumerConnector.close() hangs if ZK is unavailable and autocommit is enabled
When auto-commit is turned on, before the consumer shuts down completely it
needs to commit its last offset to ZK to avoid any duplicates consumed when
it starts over. If the ZK is not up running then the shutdown would rather
stuck than let it go and incur duplicates. This behavior is by design that
to make consistent offset maintenance, ZK should be up all the time.
On Mon, May 12, 2014 at 9:59 AM, Yury Ruchin <[EMAIL PROTECTED]> wrote: