Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.13.0, 3.14.0
-
None
-
Unknown
Description
In version 3.13.0 behaviour of scheduled consumers helath checks was changed. Consumer is considered DOWN until at least one successful execution - CAMEL-17168.
In case of rarely executed routes (i.e. once a day), consumer could be DOWN for several hours. It causes Camel context to be DOWN and in our case whole Spring Boot application to be DOWN.
Our workaround is to disable consumers healthchecks, but it's a shame to give up on this nice feature.
Possible solution would be to add configuration option to enable old health logic for specific consumers, or at least on whole context.
I'm willing to provide patch but I want to discuss optimal solution.
Attachments
Issue Links
- relates to
-
CAMEL-17436 camel-spring-boot - Disabling health check for single route or consumer is not possible
- Resolved