[OpenNMS/opennms] a5270b: NMS-19979: scope the outstanding alarm query to on...
Marshall Massengill via opennms-cvs <[email protected]>
| Newsgroups | gmane.network.opennms.cvs |
|---|---|
| Message-ID | <OpenNMS/opennms/push/refs/heads/mm/NMS-19979-smoke/[email protected]> |
Branch: refs/heads/mm/NMS-19979-smoke
Home: https://github.com/OpenNMS/opennms
Commit: a5270b15c01a1c54555fd4185a900738ec0941ca
https://github.com/OpenNMS/opennms/commit/a5270b15c01a1c54555fd4185a900738ec0941ca
Author: Marshall Massengill <[email protected]>
Date: 2026-08-11 (Tue, 11 Aug 2026)
Changed paths:
M opennms-services/src/main/java/org/opennms/netmgt/collectd/Collectd.java
M opennms-services/src/test/java/org/opennms/netmgt/collectd/CollectdOutstandingFailuresIT.java
Log Message:
-----------
NMS-19979: scope the outstanding alarm query to one node on the event paths
The event driven paths schedule a single node, or a single service on a
single node, and fire far more often than a full scheduling pass, so they
have no reason to load the outstanding data collection alarms of every
other node. scheduleNode() and the single-tuple scheduleInterface() now
pass their nodeId through to the query; the full pass is unchanged.
Covered by a second case in CollectdOutstandingFailuresIT, which raises an
alarm on a second node and asserts the node scoped query leaves it out.
To unsubscribe from these emails, change your notification settings at https://github.com/OpenNMS/opennms/settings/notifications
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/wiki/index.php?page=MailingListFaq
opennms-cvs mailing list
To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-cvs