Hi,
When using the Kafka 4.0.0 client, we could enable shared consumers by
providing the following properties in an embedded Kafka environment.
For example,
"unstable.api.versions.enable=true",
"group.coordinator.rebalance.protocols=classic,share",
"share.coordinator.state.topic.replication.factor=1",
"share.coordinator.state.topic.min.isr=1"
When upgrading to Kafka 4.1.0, the same tests work with just the last
two properties. Is that expected? (Basically, I don't need to set
unstable.api.versions.enable or group.coordinator.rebalance.protocols
in 4.1.0).
The documentation shows something like setting share.version to 1
using the kafka-features.sh script? I am curious why the embedded
Kafka cluster worked without going through this procedure.
I really appreciate any help you can provide.
Soby Chacko
When using the Kafka 4.0.0 client, we could enable shared consumers by
providing the following properties in an embedded Kafka environment.
For example,
"unstable.api.versions.enable=true",
"group.coordinator.rebalance.protocols=classic,share",
"share.coordinator.state.topic.replication.factor=1",
"share.coordinator.state.topic.min.isr=1"
When upgrading to Kafka 4.1.0, the same tests work with just the last
two properties. Is that expected? (Basically, I don't need to set
unstable.api.versions.enable or group.coordinator.rebalance.protocols
in 4.1.0).
The documentation shows something like setting share.version to 1
using the kafka-features.sh script? I am curious why the embedded
Kafka cluster worked without going through this procedure.
I really appreciate any help you can provide.
Soby Chacko
Comments
Post a Comment