Details
-
Type:
Bug
-
Status: Gathering Impact (View Workflow)
-
Priority:
Low
-
Resolution: Unresolved
-
Affects Version/s: 7.6.1, 7.8.4
-
Fix Version/s: None
-
Component/s: Administration - Workflows
-
Labels:
-
Introduced in Version:7.06
-
Support reference count:1
-
Symptom Severity:Severity 3 - Minor
-
UIS:0
-
Bug Fix Policy:
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
- is caused by
-
JRASERVER-69114 BeeHive DatabaseClusterLock leaves left-over rows in 'clusterlockstatus' table.
-
- Gathering Impact
-
- is cloned from
-
JRASERVER-68477 Workflow scheme actions leave left-over rows in 'clusterlockstatus' table.
-
- Gathering Impact
-
- relates to
-
JRASERVER-66597 JIRA DC might lose Cluster lock due database connectivity problems
-
- Closed
-