Hi Azeez,
Actually we analyzed the OOM issue and figured out that it's from BRS side
[1] and at the moment we fixed it for stateless rule sessions. But there
are limitations for stateful rule sessions.
When request is received by BRS, It creates knowledgeSession from
KnowledgeBase and feed facts
Saying just a node went OOM is has no value. Also seeing a Hazelcast error
in the stacktrace doesn't necessarily mean Hazelcast caused your node to go
OOM. You have to profile and see why it is going OOM.
On Thu, Nov 19, 2015 at 10:18 AM, Milinda Perera wrote:
> Hi,
>
> In BRS 220 snapshot (with
Hi,
In BRS 220 snapshot (with kernel upgraded to 442), in clustered setup (in
our test 3 nodes). We did load test targeting one node (lets say node3) to
a Stateful rule service until it goes OOM, and following are the errors
shown in two nodes:
* CacheCleanup error is shown from one of the nodes
