Hey Kafka Users, I've been observing a few instances of CommitFailedException (group has already rebalanced) that seem to happen well-within max.poll.interval.ms since the last commit. In at least one specific case that I've looked at, between the last successful commit and the failed commit, there is a "Marking the coordinator ... dead for group ..." message.
Log excerpts / sequence, including consumer config dump: https://gist.github.com/mfenniak/46113b4e3cbe35cc54ee103cb0515f34 This is a Kafka Streams application, with Kafka Streams & brokers on 0.10.2.0. What causes the Kafka client to "Marking the coordinator ... dead for group ..."? Is it untimely heartbeat messages? Any thoughts on what would cause the commit to fail after a "dead" like that, even though it is well within my max.poll.interval.ms? Is the message "the group has already rebalanced and assigned the partitions to another member" really necessarily true? Because in this specific instance, there was only one application instance running in this consumer group, so I'm a little skeptical. Thanks all, Mathieu
