JiraDashboardStateStoreManager leave left-over rows in 'clusterlockstatus' table.

XMLWordPrintable

    • 7.06
    • 7
    • Severity 3 - Minor
    • 0

      Summary
      A problem similar to JRASERVER-68477.
      Method JiraDashboardStateStoreManager after updating/deleting Dashboards on Jira Data Center, allocation the entry in the 'clusterlockstatus' table remains left behind. The 'locked_by_node' for that row will be empty, but they pile up in large numbers.

      Steps to Reproduce

      • Run Jira DC
      •  Update/Delete Dashboard

      Expected Results
      Once the operation is done, the entry in the 'clusterlockstatus' should be removed.


      Actual Results
      'lock_name' entries like "com.atlassian.jira.dashboard.JiraDashboardStateStoreManager.dashboard-69114" pile up in the 'clusterlockstatus' table.
      One customer had over 7000 of them.

      Workaround
      
If necessary, delete the unnecessary 'lock_name' entries manually.

            Assignee:
            Unassigned
            Reporter:
            Andriy Yakovlev [Atlassian]
            Votes:
            6 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: