Magnus Edenhill

Looks like the Kerberos client is not able to connect to the KDC. Did you add your realm and kdc to /etc/krb5.conf? Can you reach the kdc from within the...

Note that the librdkafka interceptor interface does not support message mutability, they're for intercepting, not transforming/enveloping/serialization.

@jarreds You are right in that currently there is no guarantee that messages produced with librdkafka are produced in order. They most likely will be and librdkafka makes every effort...

It would be possible to void the risk of reordering by only allowing one outstanding produce request to the broker at any given time (for a specific topic-partition), but this...

Yeah, internal automatic batching is the default mode of operation, so if you produce() 1000 messages in short term order they will most likely end up in the same ProduceRequest...

That is indeed weird, try `-d security,broker,conf` to see what it thinks ssl.ca.location is initially set to. Do you have a kcat.conf or $KCAT_CONFIG?

`%7|1633023363.992|CONF|rdkafka#producer-1| [thrd:app]: ssl.ca.location = probe` for some reason it is not picking up your -X ssl.ca.location=.. try moving that argument to different places in the command line; first, last, middle..

Great find! Can you file an issue on librdkafka so we can get it fixed in the upcoming 1.8.2 releasE?

Please provide the output from `kafkacat -V`

add `-d broker` to get some debug logs