Status: Gathering Impact (View Workflow)
Affects Version/s: 7.6.1, 7.8.4
Fix Version/s: None
Component/s: Administration - Workflows
Introduced in Version:7.06
Support reference count:4
Symptom Severity:Severity 3 - Minor
Bug Fix Policy:
When deleting something in a workflow scheme on Jira Data Center, 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.
Jira Data Center 7.6.1/7.8.4 with two nodes
1. Delete a workflow scheme.
2. Once deleted, the 'clusterlockstatus' table will have a new entry like the example below (trailing number is corresponding to 'id' in 'workflowscheme' table.)
3. Repeat step 1 and another entry will be there (and so on).
Edit a workflow scheme and add or remove an issue type.
Adding issue type to workflow scheme, 2 new rows added.
Removing issue type from workflow scheme, 3 new rows added.
(trailing number corresponding to 'id' in 'workflowschemeentity')
Once the operation is done, the entry in the 'clusterlockstatus' should be removed.
'lock_name' entries like "com.atlassian.jira.workflow.DefaultWorkflowSchemeManager$WorkflowAction.DELETE_ENTITY_10105" pile up in the 'clusterlockstatus' table.
One customer had over 8000 of them.
Caused by JRASERVER-69114
If necessary, delete the unnecessary 'lock_name' entries manually.