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
GH-2443: Distinct Concurrency for Retry Containers
Resolves#2443
Optionally configure a different concurrency for retry containers.
* Add Javadocs to RetryTopicConfigurationBuilder.
* Javadoc polishing.
Copy file name to clipboardExpand all lines: spring-kafka-docs/src/main/asciidoc/retrytopic.adoc
+4
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,9 @@ NOTE: It is not necessary to also add `@EnableKafka`, if you add this annotation
46
46
Also, starting with that version, for more advanced configuration of the feature's components and global features, the `RetryTopicConfigurationSupport` class should be extended in a `@Configuration` class, and the appropriate methods overridden.
47
47
For more details refer to <<retry-topic-global-settings>>.
48
48
49
+
By default, the containers for the retry topics will have the same concurrency as the main container.
50
+
Starting with version 3.0, you can set a different `concurrency` for the retry containers (either on the annotation, or in `RetryConfigurationBuilder`).
51
+
49
52
IMPORTANT: Only one of the above techniques can be used, and only one `@Configuration` class can extend `RetryTopicConfigurationSupport`.
50
53
51
54
===== Using the `@RetryableTopic` annotation
@@ -108,6 +111,7 @@ public RetryTopicConfiguration myRetryTopic(KafkaTemplate<String, MyPojo> templa
Copy file name to clipboardExpand all lines: spring-kafka-docs/src/main/asciidoc/whats-new.adoc
+3
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,9 @@ See <<same-broker-multiple-tests>> for more information.
35
35
This feature is no longer considered experimental (as far as its API is concerned), the feature itself has been supported since 2.7, but with a greater than normal possibility of breaking API changes.
36
36
37
37
The bootstrapping of <<retry-topic>> infrastructure beans has changed in this release to avoid some timing problems that occurred in some application regarding application initialization.
38
+
39
+
You can now set a different `concurrency` for the retry containers; by default, the concurrency is the same as the main container.
0 commit comments