camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luca Burgazzoli (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CAMEL-6399) hazelcast - route policy for having one route being master, and others as slaves
Date Fri, 02 Sep 2016 13:23:21 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Luca Burgazzoli reassigned CAMEL-6399:
--------------------------------------

    Assignee: Luca Burgazzoli

> 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
>            Assignee: Luca Burgazzoli
>             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