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

Minor typo

Browse Source 
heck -> check
This commit is contained in:
fonio
2020-05-31 09:25:25 +03:00
committed by Oleg Zhurakousky
parent 0613f25800
commit 73a5e362b4
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/src/main/asciidoc/spring-cloud-stream.adoc
View File

@@ -3130,7 +3130,7 @@ For this reason, if you include a binder in the classpath, it is advised to use
If you don't have any bindings to provide for this binder, then that is an indication that you don't need to include that binder in the classpath.
Lets take a concrete situation. Imagine you have both Kafka and Kafka Streams binders present in the classpath, but only use the Kafka Streams binder in the application code, i.e. only provide bindings using the Kafka Streams binder.
Since Kafka binder is not used and it has specific checks to see if any destinations are registered, the binder health heck will fail.
Since Kafka binder is not used and it has specific checks to see if any destinations are registered, the binder health check will fail.
The top level application health check status will be reported as `DOWN`.
In this situation, you can simply remove the dependency for kafka binder from your application since you are not using it.