[rules-users] Drools Flow, threads and persistence in a clustered environment

[Knapp, Barry]

Well if this is up for a "dig" type vote, I'd have to up-vote #2.

1) You've got these three nodes assumedly all running on the same hardware, might as well utilize it all.  If one node goes down it's not a major crisis or an experiment in "let's get the ksession running on the other node" to start processing again.
2) #2 also makes your application deployment and rule deployment strategy simpler since you will not need to worry about different apps in the cluster having different configurations.


Barry



-----Original Message-----
From: rules-users-bounces at lists.jboss.org [mailto:rules-users-bounces at lists.jboss.org] On Behalf Of Alexandros Karypidis
Sent: Monday, October 05, 2009 5:02 PM
To: 'Rules Users List'
Subject: [rules-users] Drools Flow, threads and persistence in a clustered environment

Hello,

We plan to use Drools (Flow) in our application for managing
long-running processes. High-availability is important to us and
therefore we target a clustered JBoss environment with 3 nodes. We are
looking for advice on how to approach this from a Drools perspective.
Can anybody share their experiences on running Drools in a cluster? The
following scenarios come to mind:

1) A "singleton" ksession runs constantly on one of the nodes and does
all the work; it migrates when the node goes down to another machine.

2) Multiple "ksession" instances on different nodes (for distributing
load); when one fails the other picks up its processes by having a
second "ksession" instance created on it and resuming execution.

Are there any wrapper/utility libraries for Drools that help in
clustered environments?

Thank you

_______________________________________________
rules-users mailing list
rules-users at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.