You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Luca Burgazzoli (JIRA)" <ji...@apache.org> on 2016/03/01 11:25:18 UTC
[jira] [Commented] (CAMEL-6399) hazelcast - route policy for having
one route being master, and others as slaves
[ https://issues.apache.org/jira/browse/CAMEL-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173550#comment-15173550 ]
Luca Burgazzoli commented on CAMEL-6399:
----------------------------------------
It might be interesting to have a more generic "clustering-routes" based on leader election/distributed locks on top of i.e.:
- kubernetes
- etcd
- consul (i.e. https://github.com/jhberges/camel-consul-leader)
- hazelcast
> hazelcast - route policy for having one route being master, and others as slaves
> --------------------------------------------------------------------------------
>
> Key: CAMEL-6399
> URL: https://issues.apache.org/jira/browse/CAMEL-6399
> Project: Camel
> Issue Type: New Feature
> Components: camel-hazelcast
> Reporter: Claus Ibsen
> Fix For: Future
>
>
> We should look into adding a route policy functionality to camel-hazelcast. So people can use it clustered Camel apps. And have only one node run the route. And if that node dies, then another becomes master.
> Hazelcast may have som way of support this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)