Dominic Evans

@hindessm similar to https://github.com/IBM/sarama/pull/2520

Closing as presumed to have been solved. Please reopen if not

@leogr I need to re-test on 0.33.1, we have been pinned on 0.30.0 in the interim

@FedeDP awesome! thank you

Have been running falco 0.35 since 8th June without seeing any recurrence of this issue. Closing as fixed, thanks all

@AmiKotia / @VipulZopSmart if you're both on v1.34.1 or older then I'd strongly suggest upgrading to the latest version ([v1.41.0](https://github.com/IBM/sarama/releases/tag/v1.41.0)) as there have been a few fixes to the consumer...

Nothing builtin to Sarama that would do that. If your Kafka cluster or topics have custom config then I guess it’s possible that you have log retention or offset retention...

@KrylixZA if you're using the same consumer group and topics, then there's no reason why your additional pods shouldn't be able to join the group. If you're running pods then...

@dakunge whilst that's true, I thought the only way of triggering ErrClosedConsumerGroup was if the user explicitly called client.Close(), which in the example doesn't happen until after the `for keepRunning...

@Mongey you might also be interesting in the new https://github.com/aws/aws-msk-iam-sasl-signer-go library from AWS for this on top of Sarama