You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Clarify the usage of the new consumer-group protocol in the 3.7.0 version of the client
* Add a note on the usage of `EmbeddedKafka` in `kraft` mode
* Addressing PR review
Copy file name to clipboardExpand all lines: spring-kafka-docs/src/main/antora/modules/ROOT/pages/whats-new.adoc
+15Lines changed: 15 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,21 @@ For changes in earlier version, see xref:appendix/change-history.adoc[Change His
11
11
=== Kafka Client Version
12
12
13
13
This version requires 3.7.0 `kafka-clients`.
14
+
The 3.7.0 version of Kafka client introduces the new consumer group protocol.
15
+
Fore more details and it's limitations see https://cwiki.apache.org/confluence/display/KAFKA/The+Next+Generation+of+the+Consumer+Rebalance+Protocol+%28KIP-848%29+-+Early+Access+Release+Notes[KIP-848].
16
+
The new consumer group protocol is an early access release and not meant to be used in production.
17
+
It is only recommended to use for testing purposes in this version.
18
+
Therefore, Spring for Apache Kafka supports this new consumer group protocol only to the extent of such testing level support available in the `kafka-client` itself.
19
+
By default, Spring for Apache Kafka uses the classic consumer group protocol and when testing the new consumer group protocol, that needs to be opted-in via the `group.protocol` property on the consumer.
20
+
21
+
[[x32-testing-support-changes]]
22
+
=== Testing Support Changes
23
+
24
+
The `kraft` mode is disabled in `EmbeddedKafka` by default and users wanting to use the `kraft` mode must enable it.
25
+
This is due to certain instabilities observed while using `EmbeddedKafka` in `kraft` mode, especially when testing the new consumer group protocol.
26
+
The new consumer group protocol is only supported in `kraft` mode and because of this, when testing the new protocol, that needs to be done against a real Kafka cluster and not the one based on the `KafkaClusterTestKit`, which `EmbeddedKafka` is based upon.
27
+
In addition, there were some other race conditions observed, while running multiple `KafkaListener` methods with `EmbeddedKafka` in `kraft` mode.
28
+
Until these issues are resolved, the `kraft` default on `EmbeddedKafka` will remain as `false`.
0 commit comments