Emanuele Sabellico

Given your configuration you're not using the sticky assignor as `fetch.min.bytes=1, fetch.wait.max.ms=500, fetch.error.backoff.ms=0, heartbeat.interval.ms=1000, enable.auto.commit=false, enable.partition.eof=false, enable.auto.offset.store=false, max.poll.interval.ms=3000, session.timeout.ms=3000` as the default `partition.assignment.strategy` doesn't include `cooperative-sticky` could you update your...

@ericwuseattle ``` /* FIXME: Let the cgrp pass the actual eligible partition count / size_t partition_cnt = member_cnt * 10; / FIXME */ ``` that is just the estimated partition...

@ericwuseattle thanks, other helpful info is: - if you have a rebalance callback set. In that case please test without it - how many members are there in the group,...

@Quuxplusone can this be closed, after merging the fix, is #4724 solving your case?

@Quuxplusone #4667 fixes the leak because it removes the reference to the toppar but that was introduced to fix a bug because if the barrier doesn't contain the toppar but...

@krishnajain872 Please share your error message. Which OS?

I think it's very difficult to find a timing based brute force attack to guess `ServerSignatureB64` from this. Even if the connecting broker is a _Mallory_. because the `ServerSignatureB64` is...

@Quuxplusone thanks for testing it. The code respects the lock ordering policy, that is: 1. rk main lock 2. rkb lock 3. rkt lock 4. rktp lock Is your failing...

It happens because if `_GNU_SOURCE `is defined, it's using `strndup` here https://github.com/confluentinc/librdkafka/blob/2587cac70f83fced42c51f921bed325a434f5bc7/src/rdkafka_request.c#L1236 that stops at first NULL byte differently from the alternative implementation librdkafka provides. Needs to be fixed

@sgajjarhawk @anchitj is asking because there was this fix in 2.3.0 > After a possibly persisted error, such as a disconnection or a timeout, next expected sequence used to increase,...