This means that code waiting on the iterator will continue to wait forever
if rebalance fails? No exception will be thrown from the iterator?
I assume from your message that the only way to tell if a rebalance has
failed and consumers have stopped consuming is by monitoring the lag and
restarting the consumer from "outside" the code?
What Jun described is correct, currently the consumer asynchronously fails
rebalance. But you can monitor the consumer to detect when a rebalance
operation fails since that will manifest as lag on the consumer. Please see
learn about consumer lag monitoring.
On Wed, Mar 26, 2014 at 9:06 PM, Jun Rao <[EMAIL PROTECTED]> wrote: