[rules-users] drools stateful session, cluster and replication

[Mauricio Salatino]

Do you really need persistence for that scenario?
You can think in some way to cache the incoming events and then insert in
identical sessions in different nodes
those events. In the case that a node goes wrong you can have a mechanism
to recreate the state of that node.
The persistence mechanism as it is right now will persist the complete
session per event that comes in, and depending the
scenario that can be expensive.

It would be good to know what exactly are you trying to achieve with that
architecture.

My two cents..

Cheers


On Tue, Nov 15, 2011 at 6:19 AM, Rules <8085.rahul at gmail.com> wrote:

> >From the documentation i understand that statefulknowledge session can be
> persisted.
>
> Can we also replicate the session/working memory across servers and still
> be
> able to maintain the integrity of facts and rete tree ?
> Is there a way i could replicate asserted facts incrementally or do i have
> to replicate the entire session each time (i consume events from external
> systems that could bring in new facts and alter existing facts) ?
>
> I am considering an app server provided replication that uses multi
> casting/uni casting and i will have a lot of data in working memory, around
> 3 GB. what are my options if i want to replicate it across cluster ?
>
> Appreciate any help...
>
> --
> View this message in context:
> http://drools.46999.n3.nabble.com/drools-stateful-session-cluster-and-replication-tp3509139p3509139.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>



-- 
 - CTO @ http://www.plugtree.com
 - MyJourney @ http://salaboy.wordpress.com
 - Co-Founder @ http://www.jugargentina.org
 - Co-Founder @ http://www.jbug.com.ar

 - Salatino "Salaboy" Mauricio -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20111115/0887c49a/attachment.html