You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/09/06 11:12:00 UTC

[jira] [Updated] (CAMEL-17148) camel-health - Allow to configure to auto stop routes after X failed health-checks

     [ https://issues.apache.org/jira/browse/CAMEL-17148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-17148:
--------------------------------
    Fix Version/s: 3.20.0
                       (was: 3.19.0)

> camel-health - Allow to configure to auto stop routes after X failed health-checks
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-17148
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17148
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.20.0
>
>
> It can be desireable to make it possible to configure Camel to automatic stop routes that are un-healthy after they have failed for X times in a row or Y period (time).
> There can be situations where a route will attempt to poll new messages from some external system, and that keeps failing (networking issues, remote server error). 
> Some consumers are scheduled so you can configure them to backoff, but there is no general configuration for such thing.
> Instead we can either make it possible to configure this via health-check on the route, so this can control the route.
> Or we can enhance the route controller (default and supervising) to do this. However this is maybe a little bit tricker as they are designed to be only used during bootstrap and starting the routes. After routes are started then they are no longer in use.
> Using health-check seems better as you already have settings for thresholds to setup how many X in row to regard as UP or DOWN.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)