Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-4903

Set a lock_timeout for gc partition drops

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: PDB 6.12.1
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      HA
    • Story Points:
      2
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      The report and resource event garbage collections will now time out if they have to wait longer than 5 minutes (by default) to acquire the required table lock. This prevents them from blocking other related queries indefinitely, and prevents them from participating an any permanent deadlocks. See also: https://puppet.com/docs/puppetdb/latest/configure.html#PDB_GC_DAILY_PARTITION_DROP_LOCK_TIMEOUT_MS
      Show
      The report and resource event garbage collections will now time out if they have to wait longer than 5 minutes (by default) to acquire the required table lock. This prevents them from blocking other related queries indefinitely, and prevents them from participating an any permanent deadlocks. See also: https://puppet.com/docs/puppetdb/latest/configure.html#PDB_GC_DAILY_PARTITION_DROP_LOCK_TIMEOUT_MS
    • QA Risk Assessment:
      Needs Assessment

      Description

      This may well be obviated by future work to allow the gc to kick out other queries, but for now, just make sure we don't wait indefinitely for the exclusive lock we need when dropping a partition.

      While we're waiting, all other queries that touch the "parent" table will be blocked, which may be able to quickly block all command processing threads, queries, etc., for the duration.

       

        Attachments

          Activity

            People

            Assignee:
            rob.browning Rob Browning
            Reporter:
            rob.browning Rob Browning
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support