camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Jensen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-6399) hazelcast - route policy for having one route being master, and others as slaves
Date Tue, 21 Oct 2014 18:05:34 GMT

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

Nathan Jensen commented on CAMEL-6399:
--------------------------------------

In theory you should be able to do this using Hazelcast's Lock support.  http://docs.hazelcast.org/docs/3.2/manual/html/lock.html

Have a unique lock for the route, then the cluster node who successfully obtains the lock
starts the route.  The other nodes don't start the route but instead periodically try to obtain
the lock again, so that if the former owner goes down, one of the other nodes will get the
lock and start up the route.

> 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)

Mime
View raw message