[jira] [Commented] (CAMEL-10320) Provide a LeaderPolicy to ease the implementation of master/slave route/context

["Luca Burgazzoli (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-10320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948682#comment-15948682 ] 

Luca Burgazzoli commented on CAMEL-10320:
-----------------------------------------

It would also be worth adding a concept of "Route Group" so that we can have a number that makes a service and if one is not healthy we can stop them all

> Provide a LeaderPolicy to ease the implementation of master/slave route/context
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-10320
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10320
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Luca Burgazzoli
>             Fix For: 2.19.0
>
>
> I've been working on some master/slave RoutePolicy and I'm wondering
> if we can have a proper LeaderPolicy with a standardized
> implementation in Camel 3.0 so one has only to notify when a
> leadership is taken
> In addition it may be nice to have:
> - a support for Leader election from the CmelContext so the routes are
> started when the context become leader.
> - an option to warm-up routes or to keep them stopped while not leader
> Then we can also make it exposed in JMX so tooling are able to detect
> which are current master and slaves, and whatnot.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)