Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 2 Sep 2016 14:00:29 +0000 (UTC)
From: "Luca Burgazzoli (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12649471.1369561684000.479111.1472824829367@Atlassian.JIRA>
In-Reply-To: <JIRA.12649471.1369561684000@Atlassian.JIRA>
References: <JIRA.12649471.1369561684000@Atlassian.JIRA> <JIRA.12649471.1369561684271@arcas>
Subject: [jira] [Resolved] (CAMEL-6399) hazelcast - route policy for having
 one route being master, and others as slaves
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 02 Sep 2016 14:00:31 -0000


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

Luca Burgazzoli resolved CAMEL-6399.
------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: Future)
                   2.18.0

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