Dominic Evans

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

@JoshuaC215 where are we with this issue today?

@huster-hbl @nearih hmm, you’ve seen this with modern versions of sarama? Please can you detail your topics and clients, server version and general config. It’s not immediately obvious to me...

As per @slaunay above, this is believed to have been fixed in [v1.33.0](https://github.com/IBM/sarama/releases/tag/v1.33.0) and newer

Please reopen if still a problem here

We haven't seen this fail for a while now, so closing as resolved

Unlike the Java client, Sarama doesn't have an equivalent of `max.poll.records` because we don't have a sync consumer, we only provide a streaming consumer with a `Messages` channel that you...

> It does however impact consumer rebalances. What do you mean? In the Java client yes, because poll() also influences the heartbeating and the consumer will “resign” it’s participation —...

From a consumer's perspective, it's a combination of ChannelBufferSize https://github.com/IBM/sarama/blob/05cb9fa28349a2092fb03a0f781455c9a383c9e3/config.go#L478-L482 and MaxProcessingTime https://github.com/IBM/sarama/blob/05cb9fa28349a2092fb03a0f781455c9a383c9e3/config.go#L391-L408 which combine in the partition consumer's expiry ticker https://github.com/IBM/sarama/blob/05cb9fa28349a2092fb03a0f781455c9a383c9e3/consumer.go#L568-L570 Note that there is a partition consumer for...

No longer an issue since ownership handover