Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Healthcheck is not showing actual status of consumer
See original GitHub issueThe issue we had were fixed in - https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/pull/991 Although In case if real broker altering is needed and broker will have INCREMENTAL_ALTER_CONFIGS disabled, consumer will have continuous attempts to alter broker config with healthcheck being in UP status at the same time no messages will be consumed.
I feel that health check should be up only if listener container started and ready to receive messages, the issue above is only one of the possible issues we may encounter with KafkaMessageListenerContainer and I believe KafkaMessageChannelBinder should expose isRunning status of KafkaMessageListenerContainer to health endpoint.
As a result showing just a status of topics that are in use is not enough to understand if the binder is healthy and up & running.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi guys, I might work on this next week, just to be sure we all aligned is proposed idea ok with @garyrussell @sobychacko ?
Personally, my experience with the health check on spring-cloud-stream-binder-kafka is that it says healthy if it is able to simply ping the kafka endpoint BUT will not say unhealthy if there is any problem actually consuming/producing. I would be nice if this healthcheck would/could cache unhealthy requests as a temporary bad-state.