Emanuele Sabellico

Yeah, it should be solved by using the atomic `rd_atomic32_set` instead of `rd_atomic32_init`, as the source buffer isn't being used for the first time, it's either the `rkb->rkb_waitresps` or `rkb->rkb_outbufs`...

'Set' here means that they are true, not that they can be set or unset. So if all of `rd_kafka_error_is_retriable`, `rd_kafka_error_is_fatal` and `rd_kafka_error_txn_requires_abort` are `false`, then the reccomendation is to...

@flojdek Would this be clearer? `For all other errors returned from the transactional API: the current recommendation is to treat any error that has neither retriable, abortable, or fatal functions...

@Quuxplusone thanks for sharing this. Hope will help people being aware of the changes to apply before switching to `murmur2_random`, that we cannot set as default for the same reason.

@benissimo we have a list of breaking changes that we want to do in a planned major release, and this is already included. We should also deprecate them before removing...

Thanks for the report @danog. Please also send your broker advertised listeners to check if they're longer than 256

@Vikash08Mishra yes, we're scheduling the update for the release that's being published at the end of June. We try to update the precompiled binaries bundled in other Confluent clients as...

Failed commits should be retried manually if `rd_kafka_error_is_retriable(error)` is true. Otherwise the commit won't be retried automatically.

Hi @mfleming can I apply those changes or do you want to continue the PR? Thanks!

@mfleming thanks, sorry for the delay too, I'm checking it again