SpringCloud/spring-cloud-stream
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

GH-899: num.stream.threads not taking effect

Browse Source 
Binder is overriding the num.stream.threads property specified
through the binder configuration. Fixing this issue.

Adding tests to verify.

Doc changes

Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/899
This commit is contained in:
Soby Chacko
2020-05-21 16:56:19 -04:00
parent 6578a996cb
commit fa0d6fe60e
4 changed files with 126 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/src/main/asciidoc/kafka-streams.adoc
View File

@@ -1628,3 +1628,6 @@ You can also use the `concurrency` property that core Spring Cloud Stream provid
When using this, you need to use it on the consumer.
When you have more than one input bindings either in a function or `StreamListener`, set this on the first input binding.
For e.g. when setting `spring.cloud.stream.bindings.process-in-0.consumer.concurrency`, it will be translated as `num.stream.threads` by the binder.
If you have multiple processors and one processor defines binding level concurrency, but not the others, those ones with no binding level concurrency will default back to the binder wide property specified through
`spring.cloud.stream.binder.configuration.num.stream.threads`.
If this binder configuration is not available, then the application will use the default set by Kafka Streams.