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

Newts: When Cassandra Cluster is unavailable, OpenNMS gives up on trying to contact it again

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Meridian-2016.1.0, Meridian-2016.1.1, Meridian-2016.1.2, 18.0.1, 18.0.2, Meridian-2016.1.3
    • Fix Version/s: 18.0.3, Meridian-2016.1.4
    • Component/s: Data Output - Newts
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Environment:
      Centos
    • Sprint:
      Horizon - Nov 2nd

      Description

      Hi!

      We recently ran into a situation where both of our Cassandra Servers were unavailable to OpenNMS for a couple of minutes. Even though those Servers were able to respond a short while after, OpenNMS didn't try to reconnect to them and didn't send any collected performance data to Casssandra. The logs revealed an exception which occured because of the connection loss. Only after restarting OpenNMS, the connection was re-established.

      Please change the behaviour of OpenNMS in case of connection loss to all Cassandra Servers, so it tries to reconnect "some time" after the incident.

      Thank you!

        Attachments

          Activity

            People

            Assignee:
            j-white Jesse White
            Reporter:
            sebastian.kordzik Sebastian Kordzik (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration