Sharing of working memory/facts across kie servers

[Chaitra]

Hi,

We are planning to have a cluster of kie server for a specific groups. Earlier we had issues like if one kie server goes down, the working memory/facts present in it were gone, which affected the rule processing.

Recently we came across below link

http://mswiderski.blogspot.com.br/2016/04/kie-server-clustering-and-scalability.html

This provides information about having different kie server for different department, which is what we require.

We wanted to know if one of the kie server goes down will the working memory be shared/ passed to one more kie server?

If its not shared, can we configure extrenal memory where kie server could cache there working memory?

Thanks and Regards

Chaitra

[Maciej Swiderski]

Chaitra,

On 02.06.2016, at 18:01, Chaitra <chaith...@gmail.com> wrote:

Hi,

We are planning to have a cluster of kie server for a specific groups. Earlier we had issues like if one kie server goes down, the working memory/facts present in it were gone, which affected the rule processing.

Recently we came across below link

http://mswiderski.blogspot.com.br/2016/04/kie-server-clustering-and-scalability.html

This provides information about having different kie server for different department, which is what we require.

We wanted to know if one of the kie server goes down will the working memory be shared/ passed to one more kie server?

no, working memory is completely in memory at the moment so I won’t be replicated in anyway. 

If its not shared, can we configure extrenal memory where kie server could cache there working memory?

nope, that is not possible at the moment, there is some work around this to support it. 

Please note that this applies to rules side only as for process side the working memory is persisted. So it survives server restarts. Meaning if you use processes and rules (via jbpm extension) your working memory is then stored in db. Though keep in mind it might affect performance whent he working memory is big.

Maciej

Thanks and Regards

Chaitra

--
You received this message because you are subscribed to the Google Groups "Drools Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drools-setup...@googlegroups.com.
To post to this group, send email to drools...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/drools-setup/cf7bcce2-cc27-4db0-a422-a84e17bf6974%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chaitra]

Hi Maciej

Thanks for your reply. When we say "process side the working memory is persisted" is it stored in any files or db.

So we can store the working memory in db and when server comes back up , can the server read the data back from db?

Is there any specific db should be used for this scenario?

[Maciej Swiderski]

W dniu piątek, 3 czerwca 2016 Chaitra <chaith...@gmail.com> napisał(a):

Hi Maciej

Thanks for your reply. When we say "process side the working memory is persisted" is it stored in any files or db.

Yes, it's stored in db 

So we can store the working memory in db and when server comes back up , can the server read the data back from db?

Correct 

Is there any specific db should be used for this 

Almost any rdbms can be used, underneeth there is jpa/hibernate used that takes care of db specific stuff

Maciej 

To view this discussion on the web visit https://groups.google.com/d/msgid/drools-setup/8cd80a4e-9285-47f4-89c4-a68ff77064e6%40googlegroups.com.

[Chaitra]

Thanks lot.

To unsubscribe from this group and stop receiving emails from it, send an email to drools-setup+unsubscribe@googlegroups.com.