Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-17320

DB locking pollutes DB error log

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 7.12.3, 6.23.7
    • Component/s: None
    • Labels:
    • Severity:
      High
    • Regression:
      Yes
    • Release Notes:
      Yes

      Description

      Starting Artifactory 6.0 we have moved to DB locking rather then HZ.

      Since then, if there is a lock and there is a failed write due to this, an error will be written to the DB log similar to:

      2018-08-05 19:00:06 UTC:10.6.10.67(54186):artifactory@artifactory:[130208]:ERROR:  duplicate key value violates unique constraint "locks_pk"
      2018-08-05 19:00:06 UTC:10.6.10.67(54186):artifactory@artifactory:[130208]:DETAIL:  Key (category, lock_key)=(generic, flushStatsSemaphore) already exists.
      2018-08-05 19:00:06 UTC:10.6.10.67(54186):artifactory@artifactory:[130208]:STATEMENT:  insert into distributed_locks values($1,$2,$3,$4,$5,$6)
      

      Such duplicate key violations may occur a lot, and really pollute the DB log.
      This should not be written to DB log as an ERROR, as users want to monitor this log for ERRORs.

        Attachments

          Issue Links

            Activity

                People

                Assignee:
                hezic Hezi Cohen
                Reporter:
                arielk Ariel Kabov
                Votes:
                10 Vote for this issue
                Watchers:
                30 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: