Hi Gonzalo,
So, the message conversion is because you enabled server compression with
type zstd.
If you remove the config ["compression.type" = "zstd"] in broker,
everything should be fine.
> I tried disabling zstd, but ProduceMessageConversionsPerSec remained at
the same level
Maybe you need to
Hey Luke, thanks for your reply.
We run:
- Brokers: 3.3.1
- Java Clients:
- Confluent "7.3.1-ccs"
- Kafka official "3.3.2"
We are running on AWS MSK, and using some minimal configuration:
```
# Security
"allow.everyone.if.no.acl.found" = false
"auto.create.topics.enable" = false
# Guard
Frank,
The configs are being compared after ConfigProviders have been resolved.
This is happening both as a Connector config (by
ClusterConfigState::connectorConfig) and as task configs (by
ClusterConfigState::taskConfig).
This means that two configurations that have different direct contents (the
I'm still having trouble understanding how the configs could match in the code
you highlighted when we change connector and/or task config values when no keys
are being pruned by the connector implementations in question.Would capturing a
new generation value within the config itself on every s
