<div dir="ltr">Hi all,<div><br></div><div>we observe a strange behavior with one of our rules. After deployment and sending lots of events (~150,000 of type "a"), the server slows down rapidly until it runs out of memory.</div>
<div style>We checked with VisualVM which objects are filling the memory: In one moment there were almost 14GB of NotNodeLeftTuples (88,933,186 Instances)!</div><div style><br></div><div style>This is our rule:</div><div>
<div><br></div><div><div>rule "example"</div><div><span class="" style="white-space:pre"> </span>when</div><div><span class="" style="white-space:pre"> </span>$evt1:EventObject(type=='a', $id:data['id'], $user:user) from entry-point internalstream</div>
<div><span class="" style="white-space:pre"> </span>$evt2:EventObject(type=='a', data['id']==$id, user!=$user, $user2:user) from entry-point internalstream</div><div><span class="" style="white-space:pre"> </span>not(EventObject(type=='b', user==$user, data['friendid']==$user2) from entry-point internalstream)</div>
<div><span class="" style="white-space:pre"> </span>then</div><div><span class="" style="white-space:pre"> </span>EventObject evt = new EventObject();</div><div><span class="" style="white-space:pre"> </span>evt.setType('b');</div>
<div><span class="" style="white-space:pre"> </span>evt.setUser($evt1.getUser());</div><div><span class="" style="white-space:pre"> </span>evt.put('friendid', $evt2.getUser());</div><div><span class="" style="white-space:pre"> </span>entryPoints['internalstream'].insert(evt);<span class="" style="white-space:pre"> </span> </div>
<div>end</div></div></div><div><br></div><div style>Is that behavior correct for such a size of event combinations when using a NOT in the rule?</div><div style><br></div><div style>Thanks,</div><div style>Svenja</div></div>