Jira (PDB-4903) Set a lock_timeout for gc partition drops

Issue Type:	Improvement
Assignee:	Rob Browning
Created:	2020/09/24 3:42 PM
Priority:	Normal
Reporter:	Rob Browning

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

Rob Browning (Jira)

unread,

Sep 24, 2020, 6:55:03 PM9/24/20

to puppe...@googlegroups.com

Rob Browning updated an issue

PuppetDB /

Change By:	Rob Browning

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.

Rob Browning (Jira)

unread,

Oct 19, 2020, 6:57:03 PM10/19/20

to puppe...@googlegroups.com

Rob Browning updated an issue

PuppetDB /

Change By:	Rob Browning
Release Notes:	Bug Fix
Release Notes Summary:	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.
Issue Type:	Improvement Bug

Rob Browning (Jira)

unread,

Oct 19, 2020, 7:37:03 PM10/19/20

to puppe...@googlegroups.com

Rob Browning updated an issue

PuppetDB /

https://puppet.com/docs/puppetdb/latest/configure.html#sync-settings-puppet-enterprise-only

Change By:

Rob Browning

Release Notes Summary:

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