Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-69113

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

    XMLWordPrintable

    Details

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated: