Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-74292

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

XMLWordPrintable

    • 8.2
    • 31
    • Severity 3 - Minor
    • 10
    • Hide
      Atlassian Update – 22 October 2024

      Hi everyone,

      This issue has been reviewed by the Jira Data Center Development team. As a result of our investigation, we have decided to not fix this issue. The symptom described in this issue is an expected part of how cluster locks work and has no impact on the system. As for the alarming log message is not part of any application logs related to Jira’s cluster locks. In most cases, it’s visible only in database server logs and can be safely ignored. We have prepared a Knowledge Base article explaining this error message’s significance and answering common concerns. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Best regards,
      Jakub Reczycki
      Senior Software Engineer

      Show
      Atlassian Update – 22 October 2024 Hi everyone, This issue has been reviewed by the Jira Data Center Development team. As a result of our investigation, we have decided to not fix this issue. The symptom described in this issue is an expected part of how cluster locks work and has no impact on the system. As for the alarming log message is not part of any application logs related to Jira’s cluster locks. In most cases, it’s visible only in database server logs and can be safely ignored. We have prepared a Knowledge Base article explaining this error message’s significance and answering common concerns. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Best regards, Jakub Reczycki Senior Software Engineer

      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 or similar error is visible in the some database server's logs(for some databases on default logging configuration):

      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

      There is no workaround, this message is not part of Jira application logs so it cannot be muted by changing Jira's logging configuration. 

      Please see this Knowledge Base article for details.

              Unassigned Unassigned
              755f87a38635 Krzysztof Krysiak
              Votes:
              16 Vote for this issue
              Watchers:
              28 Start watching this issue

                Created:
                Updated:
                Resolved: