Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-9371

Minions generate storm of heartbeats after being disconnected from ActiveMQ for a long period of time

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • 19.0.0, 19.0.1, 19.1.0
    • 20.0.1
    • Minion
    • Security Level: Default (Default Security Scheme)
    • None
    • Horizon - May 24th

    Description

      The heartbeat produce on the Minion side currently schedules the heartbeats using java.util.Timer#scheduleAtFixedRate. If ActiveMQ is unreachable, or sending to ActiveMQ otherwise blocks, then this method will play catch-up when connectivity is re-established, which results in many messages being sent in succession. This can be a large number of messages if the Minion has been disconnected for a while.

      Since "older" messages can be ignored, we should simply use java.util.Timer#schedule instead.

      Also, the heartbeat do not currently include a timestamp, so it is possible for the OpenNMS instance to consume "stale" heartbeats from the broker.

      Attachments

        Activity

          People

            j-white Jesse White
            j-white Jesse White
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: