Maybe we can also give the possibility to end user to implement their own leader election policy. -- Andrea Cosentino ---------------------------------- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: [email protected] Twitter: @oscerd2 Github: oscerd
On Thursday, September 15, 2016 8:33 AM, Claus Ibsen <[email protected]> wrote: On Thu, Sep 15, 2016 at 8:14 AM, Luca Burgazzoli <[email protected]> wrote: > Hello everyone, > > 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 > > > Make sense ? > Yes it sure does. There may be an older JIRA ticket about something like this already. But it does not hurt to log a new JIRA either and mark it for 3.0 so its not forgotten. We got a bunch of components now with the route policy for this master/slave stuff, but IMHO could really benefit from a proper cluster API. Then we can also make it exposed in JMX so tooling are able to detect which are current master and slaves, and whatnot. > --- > Luca Burgazzoli -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
