Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
MIME-Version: 1.0
In-Reply-To: <164ca2d20bc3492ba7ae467aa4d3b36b@derote13de02.global.corp.sap>
References: <164ca2d20bc3492ba7ae467aa4d3b36b@derote13de02.global.corp.sap>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Thu, 12 May 2016 11:05:30 +0200
Message-ID: <CAGB5yNkRwhNy3hxmbGCZCRhLQq59FjxNg1+nP3TfadfX8pztug@mail.gmail.com>
Subject: Re: Resequencer in distributed environment
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 12 May 2016 09:05:56 -0000

Its not distributed, and its in-memory only for a single camel context.

On Thu, May 12, 2016 at 9:33 AM, Siano, Stephan <stephan.siano@sap.com> wro=
te:
> Hi,
>
> has anybody ever tried to use a resequencer in a distributed environment =
(e.g. with two cluster nodes doing message processing)? I am well aware tha=
t the sequencer pattern as such does not scale, but it might be necessary t=
o have multiple cluster nodes for availability reasons or to scale out with=
 other processing steps that are executed before the resequencer.
>
> From what I have found in the code the current resequencer implementation=
 relies on running on instance, but the documentation does not say anything=
 about it.
>
> Am I correct with my assumptions or did I miss something (e.g. some distr=
ibuted sequencer implementation in some camel component)?
>
> Has anybody successfully used the resequencer in a HA scenario (and can g=
ive some hints about the approach used for that)?
>
> Best regards
> Stephan


--=20
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2