Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-36682

Cluster Safety Job doesn't log the cache safety number on panic

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 5.7-OD-46-015, 5.8.5
    • None
    • None

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      When a Confluence DC node panics, it doesn't log the cluster safety number it used to make that decision, which is very annoying.

            [CONFSERVER-36682] Cluster Safety Job doesn't log the cache safety number on panic

            David Rizzuto added a comment -

            Yes, this was fixed.

            David Rizzuto added a comment - Yes, this was fixed.

            Petro Semeniuk (Inactive) added a comment -

            setting 5.8.5 since that where cluster fixes went in.

            Petro Semeniuk (Inactive) added a comment - setting 5.8.5 since that where cluster fixes went in.

            Petro Semeniuk (Inactive) added a comment -

            drizzuto is this one still actual? I think you nailed all bugs in cluster safety including this one.

            Petro Semeniuk (Inactive) added a comment - drizzuto is this one still actual? I think you nailed all bugs in cluster safety including this one.

            David Rizzuto added a comment -

            I also added logging and caching for which node last set the number.

            David Rizzuto added a comment - I also added logging and caching for which node last set the number.

              drizzuto David Rizzuto
              drizzuto David Rizzuto
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: