You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Luca Burgazzoli <lb...@gmail.com> on 2016/09/15 06:14:24 UTC
Camel 3.0 ideas : LeaderPolicy
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 ?
---
Luca Burgazzoli
Re: Camel 3.0 ideas : LeaderPolicy
Posted by Luca Burgazzoli <lb...@gmail.com>.
Yep I'd like something like an open LeaderElection API a user can
implement from scratch (i.e. one may want to gahve multipel eladers)
or you can define just the leadership part and the default
implementation does everything else for you.
---
Luca Burgazzoli
On Thu, Sep 15, 2016 at 8:34 AM, Andrea Cosentino
<an...@yahoo.com.invalid> wrote:
> 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: ancosen1985@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
> On Thursday, September 15, 2016 8:33 AM, Claus Ibsen <cl...@gmail.com> wrote:
> On Thu, Sep 15, 2016 at 8:14 AM, Luca Burgazzoli <lb...@gmail.com> 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
Re: Camel 3.0 ideas : LeaderPolicy
Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
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: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Thursday, September 15, 2016 8:33 AM, Claus Ibsen <cl...@gmail.com> wrote:
On Thu, Sep 15, 2016 at 8:14 AM, Luca Burgazzoli <lb...@gmail.com> 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
Re: Camel 3.0 ideas : LeaderPolicy
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Sep 15, 2016 at 8:14 AM, Luca Burgazzoli <lb...@gmail.com> 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