Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-14824

IndexChangeManagerImpl should exponentially back off when configuration store is down

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: policy
    • Labels:
    • Target Version/s:
    • Sprint:
      AM 2019.9 - Crane

      Description

      Bug description

      When the configuration store goes down, the IndexChangeManagerImpl functionality attempts to reinstate the connection almost every millisecond, and logs about the failure with stacktrace included. This can consume large amounts of disk space and makes the logs difficult to use.

      How to reproduce the issue

      Use the reproduction steps in OPENAM-14531, pyforge will shut down the configuration store (to build indexes) when AM is running, and the outcome is that the Policy debug log will grow to an unexpected size.

      Expected behaviour

      AM recognizes that the server is down, and applies delays when reconnecting to the server, similar backoff approach has been implemented elsewhere in AM already.

      Current behaviour

      AM attempts to reestablish the connection every millisecond.

        Attachments

          Activity

            People

            • Assignee:
              apforrest Andrew Forrest
              Reporter:
              peter.major Peter Major [X] (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: