Duplicate key value violates unique constraint "cluster_lock_name_idx" error appears in the log

Issue Summary

Some customers report "cluster_lock_name_idx" unique constraint violation error in logs. No other issues with application functionality are observed.

Steps to Reproduce

Inconclusive, as of yet. At least in one case it happened after importing to DC "xml-export" from Server instance.

Expected Results

If two nodes attempt to acquire a lock at the same time, unique constraint violation will happen. Such behaviour is expected and if there are no other issues with application functionality, no additional action is required.

Actual Results

The below error is visible in the atlassian-jira.log file:

2022-08-18 06:15:17.304 CEST [28256] ERROR:  duplicate key value violates unique constraint "cluster_lock_name_idx"
2022-08-18 06:15:17.304 CEST [28256] DETAIL:  Key (lock_name)=(sla_issue_update_103176) already exists.
2022-08-18 06:15:17.304 CEST [28256] STATEMENT:  insert into public.clusterlockstatus (lock_name, update_time, id)
	values ($1, $2, $3) 

Workaround

Changing the logging level would hide the error in the logs, but it is not recommended.