Memory leak in Drools engine for alarmd

Description

We've observed what appears to be a memory leak in the Drools engine for alarmd on systems processing high volumes of events & alarms.

This appears to be a regression from: https://issues.opennms.org/browse/NMS-12244

Acceptance / Success Criteria

None

Attachments

1

Lucidchart Diagrams

Activity

Jesse White October 24, 2019 at 1:43 AM

Switching from STREAM to CLOUD mode: https://github.com/OpenNMS/opennms/pull/2781

Jesse White October 11, 2019 at 2:59 PM

Didn't wait long enough, the problem is still manifesting itself. Looks more like a problem with Drools at this point.

Jesse White October 9, 2019 at 7:15 PM

PR: https://github.com/OpenNMS/opennms/pull/2756

I've update the affected system with the patch and it has been running without any problems for 72+hours now.

Fixed

Details

Assignee

Reporter

Components

Sprint

Affects versions

Priority

PagerDuty

Created October 3, 2019 at 5:52 PM
Updated October 30, 2019 at 2:09 PM
Resolved October 30, 2019 at 2:09 PM