Jira (PDB-5633) Investigate why (some?) command discards aren't including the stack
Title: Message Title Rob Browning commented on PDB-5633 Re: Investigate why (some?) command discards aren't including the stack Hmm, I don't know if there's any reliable way to provoke the behavior since it's a JVM optimization that may happen "under some circumstances": https://docs.oracle.com/javase/8/docs/api/java/lang/Throwable.html#getStackTrace-- As a practical matter, with our JVM, it sounds like it depends on various things, including whether or not the jit has decided the code is "hot" enough. I suppose you could try submitting a bunch of broken commands, and maybe it'd eventually start happening on the discards. Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484959.1682619597000.597.1686864120037%40Atlassian.JIRA.
Jira (PDB-5663) Improve sync request responses for newer requests specifying timeout
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5663 Improve sync request responses for newer requests specifying timeout Change By: Rob Browning Release Notes Summary: The PuppeDB PuppetDB HA sync version has been incremented because sync requests now specify a timeout which older servers will reject. Changing the sync version produces a more meaningful error response indicating that the versions are mismatched. Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.486935.1686764745000.9705.1686765060033%40Atlassian.JIRA.
Jira (PDB-5663) Improve sync request responses for newer requests specifying timeout
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5663 Improve sync request responses for newer requests specifying timeout Issue Type: Improvement Assignee: Rob Browning Components: PuppetDB Created: 2023/06/14 10:45 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to th
Jira (PDB-5593) Generating report data
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5593 Generating report data Change By: Rob Browning Fix Version/s: PDB 8.0.1 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481308.1676309116000.8946.1686610560030%40Atlassian.JIRA.
Jira (PDB-5645) Abandon queries when client disconnects
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5645 Abandon queries when client disconnects Change By: Rob Browning Sprint: Skeletor 06/07/2023 Issue Type: Task Improvement Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.485720.1684356145000.3774.1685556540101%40Atlassian.JIRA.
Jira (PDB-5645) Abandon queries when client disconnects
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-5645 Abandon queries when client disconnects Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.485720.1684356145000.3773.1685556540038%40Atlassian.JIRA.
Jira (PDB-5633) Investigate why (some?) command discards aren't including the stack
Title: Message Title Rob Browning commented on PDB-5633 Re: Investigate why (some?) command discards aren't including the stack So this ticket was originally intended to (at least) figure out how to fix the (presumed) pdb bug that was preventing the stack traces from printing, but after I investigated for a bit, it didn't look like there was a pdb bug. My search for other culprits didn't hit the mark, but then we think Austin probably found the cause: https://bugs.openjdk.org/browse/JDK-8273392 Assuming that's right, and perhaps even as a test to see if it's right, we thought one possible approach would be to turn that option off at one of the sites and see if the stack traces appear. That would also (more importantly in the short term) hopefully allow us to see what's causing the command failures. We think we should be able to disable the optimization, which should restore the stack traces by adding this JVM argument to the pdb invocation: -XX:-OmitStackTraceInFastThrow Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484959.1682619597000.2688.1685130120024%40Atlassian.JIRA.
Jira (PDB-5633) Investigate why (some?) command discards aren't including the stack
Title: Message Title Rob Browning assigned an issue to Unassigned PuppetDB / PDB-5633 Investigate why (some?) command discards aren't including the stack Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484959.1682619597000.2408.1685054460033%40Atlassian.JIRA.
Jira (PDB-5633) Investigate why (some?) command discards aren't including the stack
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5633 Investigate why (some?) command discards aren't including the stack Change By: Rob Browning Sprint: Skeletor 06/07/2023 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484959.1682619597000.2409.1685054460097%40Atlassian.JIRA.
Jira (PDB-5633) Investigate why (some?) command discards aren't including the stack
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-5633 Investigate why (some?) command discards aren't including the stack Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484959.1682619597000.2382.1685051460033%40Atlassian.JIRA.
Jira (PDB-5621) Move pdbext to gh actions
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5621 Move pdbext to gh actions Change By: Rob Browning Sprint: Skeletor 05/24/2023 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483780.1680113927000.14382.1684357080095%40Atlassian.JIRA.
Jira (PDB-5621) Move pdbext to gh actions
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-5621 Move pdbext to gh actions Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483780.1680113927000.14381.1684357080034%40Atlassian.JIRA.
Jira (PDB-5645) Abandon queries when client disconnects
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-5645
Abandon queries when client disconnects
Change By:
Rob Browning
Testing revealed that pdb streaming queries definitely do continue running for a while after client disconnection. Long after the client disconnected, jetty would continue to call the {{query-eng/generated-stream}} read to stream the encoded json bytes which in turn keep the database query running. The current assumption is that the reads are caused by buffering before the next network write. A stack trace from the read reveals that there's a gzip handler, but since (at least from a cursory investigation) that handler appears to rely on a Deflate instance with a 512 byte buffer (fixed?), it's probably not the key reason for the continuing reads.In any case, after further investigation, we didn't find a straightforward way to detect a client disconnection in the ring or tk-jetty9 world, but since the jetty/servlet response handler is given a {{ServletResponse}} object, which for jetty is an {{org.eclipse.jetty.server.Response}}, I wondered if that might provide access to the client connection. It does.Jetty (9 at least) handles the connection via a chain of "interceptors" attached to the {{HttpOutput}}, which is itself attached to the {{Response}}. For a trivial jetty app there's just one interceptor, while pdb includes others (the gzip "layer" at least). The jetty {{HttpOutput}} Interceptor comments say that the last link in the chain will be an HttpChannel, and for pdb, that's currently an {{HttpChannelOverHttp}} instance, and that allows direct access to the jdk {{SocketChannel}} connected to the client.Fortunately the client channel is also in non-blocking mode, and so even though the client isn't (and shouldn't be) sending any data, an attempt to read from the client channel will return 0 as long as the client is connected and -1 after it disconnects (verified via curl against both the simple test app and pdb itself). It's then straightforward to add a check in pdb's {{query-eng/body-stream}}'s {{stream-rows}} that will cause pdb to abandon the query whenever the read indicates that the client is gone.This approach relies on some assumptions: - The jetty transport is non-blocking. - The read from the client always returns -1 after a disconnect. - By the time pdb is streaming, it's acceptable to attempt to read bytes from the client, i.e. either the client won't be sending any bytes, or it's OK to discard them.It would also require a change to trapperkeeper-webserver-jetty9, because ring handlers (both in ring itself and in tk-jetty9) don't provide the response instance to the handler, just the request map. One option would be to add an {{:include-response?}} option to the {{add-ring-handler}} service method. When true the handler call would become {{(handle request-map response)}} instead of {{(handle request-map)}}.Finally, here are a couple of draft prs (with no tests) that sketch all this out, though the pdb-side relies on a {{\*pdb-response
Jira (PDB-5645) Abandon queries when client disconnects
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5645 Abandon queries when client disconnects Issue Type: Task Assignee: Unassigned Components: PuppetDB Created: 2023/05/17 1:42 PM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (PDB-5632) Accommodate statement timeouts (opt-out, etc.) in sync
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5632 Accommodate statement timeouts (opt-out, etc.) in sync Change By: Rob Browning Release Notes: Not Needed Enhancement Release Notes Summary: PuppetDB sync (PE only) now uses the query timeouts introduced in PDB-4397 to further constrain sync operations to run within the `entity-time-limit`. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484717.1682107165000.12176.1683738900065%40Atlassian.JIRA.
Jira (PDB-5633) Investigate why (some?) command discards aren't including the stack
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5633 Investigate why (some?) command discards aren't including the stack Issue Type: Task Assignee: Unassigned Created: 2023/04/27 11:19 AM Priority: Normal Reporter: Rob Browning When pdb discards a command, it includes the stacktrace via .printStackTrace (see dlo.clj), but during an escalation, the json.gz_err.txt file just had something like: Attempt 3 @ ... java.lang.NullPointerException Attempt 2 @ ... java.lang.NullPointerException Attempt 1 @ ... java.lang.NullPointerException Is that expected/intended? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-4937) Add a default statement timeout to user queries
Title: Message Title Rob Browning commented on PDB-4937 Re: Add a default statement timeout to user queries In the end we implemented timeouts both on the pdb and pg sides, though the pg side timeouts aren't as precise because pg's statement_timeouts appear to apply to each underlying fetch batch for a top-level select, rather than the select as a whole. After some discussion, including CS, we also settled on a default statement timeout of 10m, which we expect to be long enough to avoid any significant disruption of existing environments (that aren't already likely in related trouble). Ideally, it might be even lower, something we can revisit later. Assuming everything works right, that timeout should also substantially mitigate (or outright avoid) the causes of a number of serious escalations we've seen in the past, since no queries will be allowed to remain open for (sometimes) hours, unintentionally. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.375530.1603302604000.7579.1682107800027%40Atlassian.JIRA.
Jira (PDB-5632) Accommodate statement timeouts (opt-out, etc.) in sync
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5632 Accommodate statement timeouts (opt-out, etc.) in sync Change By: Rob Browning Sprint: Skeletor 04/26/2023 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484717.1682107165000.7578.1682107680024%40Atlassian.JIRA.
Jira (PDB-5632) Accommodate statement timeouts (opt-out, etc.) in sync
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5632 Accommodate statement timeouts (opt-out, etc.) in sync Issue Type: Improvement Assignee: Rob Browning Components: PuppetDB Created: 2023/04/21 12:59 PM Priority: Normal Reporter: Rob Browning Arrange for the sync queries to opt out of any query timeouts set locally or on the remote server, and to respect the entity-time-limit instead. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-4937) Add a default statement timeout to user queries
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4937 Add a default statement timeout to user queries Change By: Rob Browning Epic Link: PDB PE - 4969 35436 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.375530.1603302604000.7568.1682106840025%40Atlassian.JIRA.
Jira (PDB-4937) Add a default statement timeout to user queries
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4937 Add a default statement timeout to user queries Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: PuppetDB now supports query timeouts for queries to the `query/` endpoint via an [optional query parameter]. A [default] and a [maximum] can also be specified in the configuration. The current default is ten minutes. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.375530.1603302604000.7567.1682106780090%40Atlassian.JIRA.
Jira (PDB-5630) RHEL Platform 7 to Platform 8 upgrade failure
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5630 RHEL Platform 7 to Platform 8 upgrade failure Change By: Rob Browning Problem: On RedHat-based OSes, PuppetDB fails to start after upgrading from Platform 7 to Platform 8. EZBake controls which java we run with by setting JAVA_BIN to /usr/bin/java in our service defaults. On Debian and Redhat (at least), this is actually a symlink to java controlled by update-alternatives and alternatives respectively. RedHat's Java 8 package still has a higher alternatives priority than Java 11, so even though our PuppetDB 8 packages install java 11, the symlink at /usr/bin/java is not updated and we continue trying to use java 8. This breaks because HikariCP was updated to a version that does not run on java 8 anymore. It is also possible that we would hit this on Debian-based OSes on any installation where an admin has manually selected java 8.This does not affect PE because the hard-coded path in EZBake is to pe-java and not a java managed by update-alternatives.Option 1: Guide users through the problem manually with documentation. On RedHat, they could be instructed to install java 11 and select it as the preferred java. Con: module upgrades will not work without manual intervention.Option 2: We can use the output of the alternatives cli tools to "sniff" out available java versions and select one that will work for us even if the user has an incompatible java selected as the default java. In this case we would remove EZBake's current /etc/default/PACKAGE hard-coded JAVA_BIN=/usr/bin/java setting, but we'd still allow users to set that JAVA_BIN there to override the auto-detection (this will also maintain their ability to use a java that is not registered with the alternatives programs.Open questions: SLES? Add Comment
Jira (PDB-5630) RHEL Platform 7 to Platform 8 upgrade failure
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5630 RHEL Platform 7 to Platform 8 upgrade failure Change By: Rob Browning Problem: On RedHat-based OSes, PuppetDB fails to start after upgrading from Platform 7 to Platform 8. EZBake controls which java we run with by setting JAVA_BIN to /usr/bin/java in our service defaults. On Debian and Redhat (at least), this is actually a symlink to java controlled by update-alternatives and alternatives respectively. RedHat's Java 8 package still has a higher alternatives priority than Java 11, so even though our PuppetDB 8 packages install java 11, the symlink at /usr/bin/java is not updated and we continue trying to use java 8. This breaks because HikariCP was updated to a version that does not run on java 8 anymore. It is also possible that we would hit this on Debian-based OSes on any installation where an admin has manually selected java 8.This does not affect PE because the hard-coded path in EZBake is to pe-java and not a java managed by update-alternatives.Option 1: Guide users through the problem manually with documentation. On RedHat, they could be instructed to install java 11 and select it as the preferred java. Con: module upgrades will not work without manual intervention.Option 2: We can use the output of the alternatives cli tools to "sniff" out available java versions and select one that will work for us even if the user has an incompatible java selected as the default java. In this case we would remove EZBake's current /etc/default/PACKAGE hard-coded JAVA_BIN =/usr/bin/java setting, but still allow users to set that there to override the sniffing by setting JAVA_BIN themselves auto-detection (this will also maintain their ability to use a java that is not registered with the alternatives programs.Open questions: SLES? Add Comment
Jira (PDB-5614) Merge-up, branch, and create pipelines (Puppet Platform 7.24.0)
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-5614
Merge-up, branch, and create pipelines (Puppet Platform 7.24.0)
Change By:
Rob Browning
(Initial planned release date: 2023-04-04)Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).* [jenkins: main|https://jenkins-enterprise.delivery.puppetlabs.net/view/puppetdb/view/main/]* [jenkins: 6 7 .x|https://jenkins-enterprise.delivery.puppetlabs.net/view/puppetdb/view/ 6 7 .x/]* [travis: puppetdb|https://app.travis-ci.com/github/puppetlabs/puppetdb/branches]* [travis: pe-puppetdb-extensions|https://app.travis-ci.com/github/puppetlabs/pe-puppetdb-extensions/branches]Do merge-ups:* Merge 6 7 .x -> mainImportant: Do this for both the core puppetdb repo and thepe-puppetdb-extensions repo!These should be submitted as PRs and merged after tests pass, if there'sanything remotely interesting about the merges. If the merges are boring,then direct push is fine.SKIP ALL REMAINING STEPS - We are leaving them here until wehave a better place to document the process to create a newbranch. When we release a new Y version we do it off of main andcut a maintained branch later (if at all).Then, prepare the branch for release:* If needed, create the branch (off of main, almost certainly)* Check that there aren't any essential updates to ezbake needed in this release* Update the branch in the README's Travis CI build icon link* Update the version in project.clj in both repos. Continue to use a -SNAPSHOT version for now* Push each branch *directly* to the puppetlabs github repo.Update ci-job-configs:* https://github.com/puppetlabs/ci-job-configs/blob/main/jenkii/enterprise/projects/puppetdb.yaml#L49-L52* https://github.com/puppetlabs/ci-job-configs/blob/main/jenkii/enterprise/projects/puppetdb.yaml#L170-L180* Add a new tab to Jenkins if needed: hit the + tab in the link here https://jenkins-enterprise.delivery.puppetlabs.net/view/puppetdb/, select "list view", and add the following rule to the regex section that matches the build you're preparing. Example: (?!experimental).*puppetdb.*5.2.xUpdate travis to add a cron job for the new branch:* https://app.travis-ci.com/github/puppetlabs/puppetdb/settings* https://app.travis-ci.com/github/puppetlabs/pe-puppetdb-extensions/settingsUpdate the headers in all the puppetdb docs:* changes need to be made to the puppet-docs repo. See [this PR|https://github.com/puppetlabs/puppet-docs/pull/888/files] for an example.Update travis integration test refs:* Once Puppet and PuppetServer have created their release branches, update our testing defaults and .travis.yml file to run integration tests against the new branches. Our strategy is to test the corresponding release branches of Puppet and PuppetServer and the previous release branches for each release branch of PuppetDB.* ext/test-conf/puppet-ref-default and ext/test-conf/puppetse
Jira (PDB-5621) Move pdbext to gh actions
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5621 Move pdbext to gh actions Issue Type: Task Assignee: Unassigned Created: 2023/03/29 11:18 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483780.1680113927000.1740.1
Jira (PDB-5582) Remove metrics/v1 references
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5582 Remove metrics/v1 references Change By: Rob Browning Release Notes: Deprecation Release Notes Summary: The metrics/v1 endpoint documentation has been removed, given the endpoint's retirement. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479640.1674756239000.1426.1680054480026%40Atlassian.JIRA.
Jira (PDB-5582) Remove metrics/v1 references
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5582 Remove metrics/v1 references Change By: Rob Browning Fix Version/s: PDB 8.0.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479640.1674756239000.1425.1680054360021%40Atlassian.JIRA.
Jira (PDB-4937) Add a default statement timeout to user queries
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4937 Add a default statement timeout to user queries Change By: Rob Browning Sprint: Skeletor 03/15/2023 Story Points: 1 Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.375530.1603302604000.3947.1678307580029%40Atlassian.JIRA.
Jira (PDB-5604) Add linting kondo to puppetdb extensions too
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-5604 Add linting kondo to puppetdb extensions too Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.482013.167760689.2421.1677698580023%40Atlassian.JIRA.
Jira (PDB-5485) Move to github actions
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5485 Move to github actions Change By: Rob Browning Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.444744.1650904924000.1878.1677633360031%40Atlassian.JIRA.
Jira (PDB-5485) Move to github actions
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5485 Move to github actions Change By: Rob Browning Sprint: Skeletor 03/01/2023 Story Points: 1 Team: Dumpling Skeletor Issue Type: Improvement Task Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.444744.16509049240
Jira (PDB-5604) Add linting kondo to puppetdb extensions too
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5604 Add linting kondo to puppetdb extensions too Change By: Rob Browning Summary: Add linting kondo to puppetdb extensions too Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.482013.167760689.1572.1677607080135%40Atlassian.JIRA.
Jira (PDB-5604) Add linting to puppetdb extensions
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5604 Add linting to puppetdb extensions Issue Type: Task Assignee: Unassigned Created: 2023/02/28 9:54 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.482013.167760689000
Jira (PDB-4688) Deprecation removals for PuppetDB 8
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4688 Deprecation removals for PuppetDB 8 Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: The deprecated query streaming method has been removed, along with the associated `PDB_USE_DEPRECATED_STREAMING_METHOD` environment variable.JDK 11 has changed from supported to "tested" and JDK 17 is now supported.The previously optional PostgreSQL trigram index support, [`pg_trgm`](https://www.postgresql.org/docs/11/pgtrgm.html) is now required. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356709.1587757722000.9810.1676307180089%40Atlassian.JIRA.
Jira (PDB-5215) Diagnose and fix pdb SIGHUP handling
Title: Message Title Rob Browning commented on PDB-5215 Re: Diagnose and fix pdb SIGHUP handling This could be reliably reproduced with PuppetDB right around 7.12.1 by sending a SIGHUP after startup, but before any command had been processed. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408847.1627498028000.9157.1675965120025%40Atlassian.JIRA.
Jira (PDB-5215) Diagnose and fix pdb SIGHUP handling
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5215 Diagnose and fix pdb SIGHUP handling Change By: Rob Browning Release Notes: Bug Fix Release Notes Summary: PuppetDB should no longer crash on reload (SIGHUP) in some cases (e.g. after startup but before processing any commands). Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408847.1627498028000.9154.1675964520094%40Atlassian.JIRA.
Jira (PDB-5215) Diagnose and fix pdb SIGHUP handling
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5215 Diagnose and fix pdb SIGHUP handling Change By: Rob Browning Fix Version/s: PDB 8.0.0 Fix Version/s: PDB 7.12.2 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408847.1627498028000.9153.1675964520031%40Atlassian.JIRA.
Jira (PDB-5215) Diagnose and fix pdb SIGHUP handling
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5215 Diagnose and fix pdb SIGHUP handling Change By: Rob Browning Sprint: Skeletor 02/15/2023 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408847.1627498028000.7990.1675713360024%40Atlassian.JIRA.
Jira (PDB-5215) Diagnose and fix pdb SIGHUP handling
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5215 Diagnose and fix pdb SIGHUP handling Change By: Rob Browning Story Points: 1 Team: HA Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408847.1627498028000.7907.1675704180362%40Atlassian.JIRA.
Jira (PDB-5215) Diagnose and fix pdb SIGHUP handling
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-5215 Diagnose and fix pdb SIGHUP handling Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408847.1627498028000.7908.1675704180410%40Atlassian.JIRA.
Jira (PDB-5582) Remove/rework/redirect metrics/v1 references
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5582 Remove/rework/redirect metrics/v1 references Issue Type: Task Assignee: Unassigned Components: PuppetDB Created: 2023/01/26 10:03 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" gro
Jira (PDB-4688) Deprecation removals for PuppetDB 8
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4688 Deprecation removals for PuppetDB 8 Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356709.1587757722000.2364.1674072720028%40Atlassian.JIRA.
Jira (PDB-5571) ini4j vulnerability
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5571 ini4j vulnerability Change By: Rob Browning Fix Version/s: PDB 7.12.1 Fix Version/s: PDB 8.0.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.477999.1672956688000.72394.1673479020040%40Atlassian.JIRA.
Jira (PDB-5572) Run puppetserver in its own jvm in the :integration tests
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5572 Run puppetserver in its own jvm in the :integration tests Issue Type: Task Assignee: Rob Browning Created: 2023/01/09 2:29 PM Priority: Normal Reporter: Rob Browning ...so that we're not conflating dependencies anymore (and so that we can continue to test 6.x server against 7.x pdb). Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5571) ini4j vulnerability
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5571 ini4j vulnerability Issue Type: Bug Assignee: Rob Browning Created: 2023/01/05 2:11 PM Priority: Normal Reporter: Rob Browning clj-kitchensink imports a vulnerable version of ini4j. See https://security.snyk.io/vuln/SNYK-JAVA-ORGINI4J-3042998 It should be updated, promoted, and updated in clj-parent. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5570) Update postgres jdbc driver to 42.4.3 to address security issue
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5570 Update postgres jdbc driver to 42.4.3 to address security issue Issue Type: Bug Assignee: Rob Browning Created: 2023/01/05 2:09 PM Fix Versions: PDB 7.12.1, PDB 8.0.0 Priority: Critical Reporter: Rob Browning See https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-562r-vg33-8x8h#event-84471 main branch (promotes into PE 2021.7.x and PE 2023.0 (main)): https://github.com/puppetlabs/clj-parent/blob/0f26ad7841370f3ccb70431bb7f6c263626cada1/project.clj#L100 to 42.4.3 4.x branch (promotes into PE 2019.8.x): https://github.com/puppetlabs/clj-parent/blob/c2bb8c9cf61ba6c1c0fa2b6285ab3969894fa5b9/project.clj#L97 to 42.4.3 and ensure the parent bump is promoted into all the projects promoted into PE. Add Comment
Jira (PDB-5563) Draft release notes (Puppet Platform 7.12.0)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5563 Draft release notes (Puppet Platform 7.12.0) Change By: Rob Browning Summary: Draft release notes (Puppet Platform 7. 21 12 .0) Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.474988.1668795033000.62932.1670014080055%40Atlassian.JIRA.
Jira (PDB-5559) Ensure partition drops and migrations can eliminate all competitors
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5559 Ensure partition drops and migrations can eliminate all competitors Change By: Rob Browning Fix Version/s: PDB 7.12.0 Fix Version/s: PDB 6.22.2 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.474923.1668702253000.62857.167460045%40Atlassian.JIRA.
Jira (PDB-5559) Ensure partition drops and migrations can eliminate all competitors
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-5559
Ensure partition drops and migrations can eliminate all competitors
Change By:
Rob Browning
Release Notes:
Bug Fix
Release Notes Summary:
Make sure that partition drops and migration The coordination of report-related garbage collection has been improved. Previously, if a separate `read-database` user were configured, incoming queries could block the garbage collection. Whenever a separate `read-database` user *is* specified, the normal (write) database user must have the rights right to and always do terminate both the read and write users user's queries . See The [recommended configuration]({{puppetdb}}/configure_postgres.html) has been updated to include a suitable `grant puppetdb_read to puppetdb`.The coordination of migrations has also been improved. Previously if a separate `read-database` user were configured, it wouldn't actually be evicted during migrations. Note that the commit messages migrator user (role) must have the ability to terminate the read user's connections. The [recommended configuration]({{puppetdb}}/configure_postgres.html) accomplishes this by granting the write user's role to the migrator via the `grant puppetdb to puppetdb_migrator` , doc changes which allows the migrator to terminate the read user's connections indirectly via the write user's membership in the read user's role , and release notes for additional information as described above .
Add Comment
This message was sent by Atlassian Jira (v8.20.11#8200
Jira (PDB-5559) Ensure partition drops and migrations can eliminate all competitors
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5559 Ensure partition drops and migrations can eliminate all competitors Change By: Rob Browning Make sure that partition drops and migration coordination have the rights to and always do terminate both the read and write users. See the commit messages, doc changes, and release notes for additional information. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.474923.1668702253000.62569.1669918140027%40Atlassian.JIRA.
Jira (PDB-5559) Ensure partition drops and migrations can eliminate all competitors
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5559 Ensure partition drops and migrations can eliminate all competitors Change By: Rob Browning Release Notes Summary: Make sure that partition drops and migration coordination have the rights to and always do terminate both the read and write users. See the commit messages, doc changes, and release notes for additional information. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.474923.1668702253000.62568.1669917840035%40Atlassian.JIRA.
Jira (PDB-5559) Ensure partition drops and migrations can eliminate all competitors
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5559 Ensure partition drops and migrations can eliminate all competitors Change By: Rob Browning Summary: Ensure partition drops and migrations can eliminate all relevant/expected blockers competitors Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.474923.1668702253000.62567.1669916580057%40Atlassian.JIRA.
Jira (PDB-5559) Ensure partition drops can eliminate all relevant/expected blockers
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5559 Ensure partition drops can eliminate all relevant/expected blockers Issue Type: Bug Assignee: Rob Browning Components: PuppetDB Created: 2022/11/17 8:24 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google G
Jira (PDB-5559) Ensure partition drops can eliminate all relevant/expected blockers
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5559 Ensure partition drops can eliminate all relevant/expected blockers Change By: Rob Browning Sprint: Skeletor 11/23/2022 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.474923.1668702253000.59168.1668702300104%40Atlassian.JIRA.
Jira (PDB-5548) Partition GC's query bulldozer not guaranteed to make progress
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5548 Partition GC's query bulldozer not guaranteed to make progress Change By: Rob Browning Release Notes Summary: PuppetDB should drop old partitions (e.g. reports) more effectively.Because dropping the partitions currently requires an exclusive lock that can block all all other queries, PuppetDB tries to eliminate any queries that are blocking a drop attempt, but the method previously used to stop queries was insufficient. In addition, as constructed right now, competing queries can deadlock with the drop attempt. If a deadlock doesn't resolve within the configured `deadlock_timeout`, PostgreSQL's deadlock detector will break the deadlock, and to do so in some cases it has chosen to kill the partition drop attempt every time.To fix this problem, PuppetDB now terminates any queries competing with a drop attempt via `pg_terminate_backend` instead of `pg_cancel_backend`. This should be very reliable (cancel was more advisory), and PuppetDB also makes sure that it has the connection it needs for the terminations before it makes making a drop attempt. Finally, it will try to issue those terminations termination requests more frequently than it did before (every fifth of a second instead of every second). Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5548) Partition GC's query bulldozer not guaranteed to make progress
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5548 Partition GC's query bulldozer not guaranteed to make progress Change By: Rob Browning Release Notes: Bug Fix Release Notes Summary: PuppetDB should drop old partitions (e.g. reports) more effectively.Because dropping the partitions currently requires an exclusive lock that can block all all other queries, PuppetDB tries to eliminate any queries that are blocking a drop attempt, but the method previously used to stop queries was insufficient. In addition, as constructed right now, competing queries can deadlock with the drop attempt. If a deadlock doesn't resolve within the configured `deadlock_timeout`, PostgreSQL's deadlock detector will break the deadlock, and to do so in some cases it has chosen to kill the partition drop attempt every time.To fix this problem, PuppetDB now terminates any queries competing with a drop attempt via `pg_terminate_backend` instead of `pg_cancel_backend`. This should be very reliable (cancel was more advisory), and PuppetDB also makes sure that it has the connection it needs for the terminations before it makes a drop attempt. Finally, it will try to issue those terminations more frequently than it did before (every fifth of a second instead of every second). Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5548) Partition GC's query bulldozer not guaranteed to make progress
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5548 Partition GC's query bulldozer not guaranteed to make progress Change By: Rob Browning Fix Version/s: PDB 6.22.2 Fix Version/s: PDB 7.12.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.470479.1664997895000.56028.1667837280107%40Atlassian.JIRA.
Jira (PDB-5548) Partition GC's query bulldozer not guaranteed to make progress
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-5548 Partition GC's query bulldozer not guaranteed to make progress Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.470479.1664997895000.53591.1666937400062%40Atlassian.JIRA.
Jira (PDB-5548) Partition GC's query bulldozer not guaranteed to make progress
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5548 Partition GC's query bulldozer not guaranteed to make progress Change By: Rob Browning Team: Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.470479.1664997895000.50036.1666281300043%40Atlassian.JIRA.
Jira (PDB-5524) Log producer timestamp, hash, and disposition for commands
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5524 Log producer timestamp, hash, and disposition for commands Change By: Rob Browning Release Notes: Enhancement Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.462921.1660766501000.43670.1665172980034%40Atlassian.JIRA.
Jira (PDB-5524) Log producer timestamp, hash, and disposition for commands
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5524 Log producer timestamp, hash, and disposition for commands Change By: Rob Browning Fix Version/s: PDB 7.11.2 Fix Version/s: PDB 6.22.2 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.462921.1660766501000.21060.1661357880189%40Atlassian.JIRA.
Jira (PDB-5524) Log producer timestamp, hash, and disposition for commands
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5524 Log producer timestamp, hash, and disposition for commands Change By: Rob Browning Release Notes Summary: PuppetDB will now log additional information when processing each command, including the producer timestamp, and when available, a prefix of the fingerprint. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.462921.1660766501000.19162.1661187420081%40Atlassian.JIRA.
Jira (PDB-5524) Log producer timestamp, hash, and disposition for commands
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5524 Log producer timestamp, hash, and disposition for commands Change By: Rob Browning Sprint: Dumpling 8/30/22 Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.462921.1660766501000.19157.1661187300130%40Atlassian.JIRA.
Jira (PDB-5524) Log producer timestamp, hash, and disposition for commands
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5524 Log producer timestamp, hash, and disposition for commands Issue Type: Improvement Assignee: Rob Browning Components: PuppetDB Created: 2022/08/17 1:01 PM Priority: Normal Reporter: Rob Browning Add the producer timestamp, hash, and final status to the "command processed for CERTNAME" log messages. This will make it much easier to diagnose various problems, including sync issues. Add Comment This message was sent by Atlassia
Jira (PDB-5515) Rework sync timeouts to accomodate jdbc ignoring interrupts
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5515 Rework sync timeouts to accomodate jdbc ignoring interrupts Change By: Rob Browning The recent sync changes to avoid blocking forever depend on thread interrupts which it turns out jdbc doesn't always respect. Rework the timeouts to avoid depending on interrupts. Recommend the chapter in the "train book" (Java Concurrency in Practice) on "Cancellation and Shutdown" for background, for anyone not already familiar with the expectations -- briefly, thread interruption is cooperative, and it turns out the jdbc driver (perhaps intentionally) doesn't cooperate.The current plan is to adjust the pull-records-from-remote code to replace interruption with (diminishing) in-transaction timeouts in all the relevant transactions (remote summary query, batch transfer process, etc.). Ideally, the timeout should be based on the entity-ttl, and should be reduced after each command to respect the overall ttl as the sync process proceeds. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5515) Rework sync timeouts to accomodate jdbc ignoring interrupts
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5515 Rework sync timeouts to accomodate jdbc ignoring interrupts Change By: Rob Browning Summary: Rework sync timeouts to handle accomodate jdbc ignoring interrupts Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.455584.1658250232000.9208.1660060620038%40Atlassian.JIRA.
Jira (PDB-5517) Don't fail upgrade_latest acceptance test between tagging and release
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5517 Don't fail upgrade_latest acceptance test between tagging and release Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2022/08/02 1:40 PM Priority: Normal Reporter: Rob Browning Right now upgrade_latest fails between tagging and the actual release because of the way it picks versions. It stops failing once the new packages are actually available via yum. Change it to remain green during that period so we don't have to remember we should ignore it. While we may still want a pre-flight check like that to run just before announcing a release, it might belong elsewhere. Add Comment
Jira (PDB-5260) Improve PQL parse performance with high number of filter clauses
Title: Message Title Rob Browning commented on PDB-5260 Re: Improve PQL parse performance with high number of filter clauses Oh, and also we did address the earlier, immediate problem by rewriting some of the production rules – was sufficient for at least that case. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.414914.1631118889000.4656.1659029220081%40Atlassian.JIRA.
Jira (PDB-5260) Improve PQL parse performance with high number of filter clauses
Title: Message Title Rob Browning commented on PDB-5260 Re: Improve PQL parse performance with high number of filter clauses Just to record this here, another case that if relevant might nudge us toward fixing it more comprehensively is any situations where we accept user pql or user pql fragments (from some ui) that we combine into a broader query. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.414914.1631118889000.4654.1659029160113%40Atlassian.JIRA.
Jira (PDB-5515) Rework sync timeouts to handle jdbc ignoring interrupts
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5515 Rework sync timeouts to handle jdbc ignoring interrupts Change By: Rob Browning Sprint: Dumpling Ready to Groom Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.455584.1658250232000.64896.1658250420045%40Atlassian.JIRA.
Jira (PDB-5515) Rework sync timeouts to handle jdbc ignoring interrupts
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5515 Rework sync timeouts to handle jdbc ignoring interrupts Issue Type: Bug Assignee: Unassigned Created: 2022/07/19 10:03 AM Priority: Normal Reporter: Rob Browning The recent sync changes to avoid blocking forever depend on thread interrupts which it turns out jdbc doesn't always respect. Rework the timeouts to avoid depending on interrupts. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PDB-5498) Evaluate/update dependencies
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5498 Evaluate/update dependencies Issue Type: Improvement Assignee: Unassigned Created: 2022/05/31 8:55 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.450632.165401255300
Jira (PDB-5483) PuppetDB ERROR: cannot set transaction read-write mode during recovery After Upgrade to 7.10
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5483 PuppetDB ERROR: cannot set transaction read-write mode during recovery After Upgrade to 7.10 Change By: Rob Browning Release Notes: Bug Fix Release Notes Summary: The approach taken in the previous changes (cf. PDB-5483) to disable the jit was incompatible with PostgreSQL hot standbys: https://www.postgresql.org/docs/current/hot-standby.html#HOT-STANDBY-USERSThe method of disabling the jit has been changed to avoid the problem. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.443567.1649882285000.37227.1653506940035%40Atlassian.JIRA.
Jira (PDB-5483) PuppetDB ERROR: cannot set transaction read-write mode during recovery After Upgrade to 7.10
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5483 PuppetDB ERROR: cannot set transaction read-write mode during recovery After Upgrade to 7.10 Change By: Rob Browning Fix Version/s: PDB 6.21.1 Fix Version/s: PDB 7.11.0 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.443567.1649882285000.37222.1653506760051%40Atlassian.JIRA.
Jira (PDB-5483) PuppetDB ERROR: cannot set transaction read-write mode during recovery After Upgrade to 7.10
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-5483 PuppetDB ERROR: cannot set transaction read-write mode during recovery After Upgrade to 7.10 Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.443567.1649882285000.36358.1653414060193%40Atlassian.JIRA.
Jira (PDB-5333) Allow retrieving the pdb version without a db query
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5333 Allow retrieving the pdb version without a db query Change By: Rob Browning Fix Version/s: PDB 7.11.0 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.419848.1634571298000.33888.1652995140034%40Atlassian.JIRA.
Jira (PDB-5333) Allow retrieving the pdb version without a db query
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5333 Allow retrieving the pdb version without a db query Change By: Rob Browning Fix Version/s: PDB 7.11.0 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.419848.1634571298000.33886.1652995080063%40Atlassian.JIRA.
Jira (PDB-5333) Allow retrieving the pdb version without a db query
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5333 Allow retrieving the pdb version without a db query Change By: Rob Browning Fix Version/s: PDB 7.11.0 Fix Version/s: PDB 6.21.1 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.419848.1634571298000.33887.1652995080113%40Atlassian.JIRA.
Jira (PDB-5333) Allow retrieving the pdb version without a db query
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5333 Allow retrieving the pdb version without a db query Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: The status endpoint (/status/v1/services/puppetdb-status) now implements trapperkeeper-status levels, in particular specifying `level=critical` can make the query notably less expensive by avoiding any database queries. Currently, the `:status` will just be `null` when the level is critical. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.419848.1634571298000.33884.1652995020055%40Atlassian.JIRA.
Jira (PDB-5483) PuppetDB ERROR: cannot set transaction read-write mode during recovery After Upgrade to 7.10
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5483 PuppetDB ERROR: cannot set transaction read-write mode during recovery After Upgrade to 7.10 Change By: Rob Browning Affects Version/s: PDB 6.21.0 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.443567.1649882285000.33800.1652988900067%40Atlassian.JIRA.
Jira (PDB-5493) Update ticket templates (Puppet Platform 7.17.0)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5493 Update ticket templates (Puppet Platform 7.17.0) Change By: Rob Browning Sprint: Dumpling 5-24-22 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.446177.1651536017000.33795.1652988181082%40Atlassian.JIRA.
Jira (PDB-5490) Draft release notes (Puppet Platform 7.17.0)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5490 Draft release notes (Puppet Platform 7.17.0) Change By: Rob Browning Sprint: Dumpling 5-24-22 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.446174.1651535994000.33792.1652988180937%40Atlassian.JIRA.
Jira (PDB-5488) Merge-up, branch, and create pipelines (Puppet Platform 7.17.0)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5488 Merge-up, branch, and create pipelines (Puppet Platform 7.17.0) Change By: Rob Browning Sprint: Dumpling 5-24-22 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.446172.1651535985000.33790.1652988180839%40Atlassian.JIRA.
Jira (PDB-5491) Bump versions, push directly, and tag (Puppet Platform 7.17.0)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5491 Bump versions, push directly, and tag (Puppet Platform 7.17.0) Change By: Rob Browning Sprint: Dumpling 5-24-22 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.446175.1651536008000.33793.1652988180986%40Atlassian.JIRA.
Jira (PDB-5492) Check builds, promote to PE (Puppet Platform 7.17.0)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5492 Check builds, promote to PE (Puppet Platform 7.17.0) Change By: Rob Browning Sprint: Dumpling 5-24-22 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.446176.1651536012000.33794.1652988181034%40Atlassian.JIRA.
Jira (PDB-5489) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.17.0)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5489 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.17.0) Change By: Rob Browning Sprint: Dumpling 5-24-22 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.446173.165153599.33791.1652988180890%40Atlassian.JIRA.
Jira (PDB-5492) Check builds, promote to PE (Puppet Platform 7.17.0)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5492 Check builds, promote to PE (Puppet Platform 7.17.0) Change By: Rob Browning Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.446176.1651536012000.33761.1652987940185%40Atlassian.JIRA.
Jira (PDB-5481) Update ticket templates (Puppet Platform 7.16.0)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5481 Update ticket templates (Puppet Platform 7.16.0) Change By: Rob Browning Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.442380.1648659647000.33704.1652983680050%40Atlassian.JIRA.
Jira (PDB-5496) Rework/augment critical timeouts, given jdbc not interruptable
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5496 Rework/augment critical timeouts, given jdbc not interruptable Issue Type: Bug Assignee: Unassigned Created: 2022/05/10 9:42 AM Priority: Normal Reporter: Rob Browning It turns out some jdbc operations do not respect thread interrupts (double-check that, austin.blatt and I have some context), and recent important stability/performance improvements (e.g. sync timeouts), were written under the assumption that they do (I'll plan to link some relevant tickets). Assuming interrupts won't always work, rewrite the code to accommodate that. Possibilities include (also) cancelling the statement (evaluate what pgjdbc supports there), setting a query timeout (investigate Statement.setQueryTimeout, or in-line per-transaction set commands to establish a timeout), etc. Add Comment
Jira (PDB-5495) Investigate observed slow/expensive environment gc query
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-5495
Investigate observed slow/expensive environment gc query
Change By:
Rob Browning
While evaluating an escalation, this was noticed in the logs:{code}LOG: duration: 3.734 ms execute : DELETE FROM environments WHERE ID NOT IN (SELECT environment_id FROM catalogs WHERE environment_id IS NOT NULLUNION SELECT environment_id FROM reportsWHERE environment_id IS NOT NULLUNION SELECT environment_id FROM factsetsWHERE environment_id IS NOT NULL)LOG: temporary file: path "pg_tblspc/16400/PG_11_...", size 127286260{code}This ticket's a reminder to evaluate whether that's actually the query we want, e.g. union vs union all, etc.
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an
Jira (PDB-5495) Investigate observed slow/expensive environment gc query
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-5495
Investigate observed slow/expensive environment gc query
Change By:
Rob Browning
While evaluating an escalation, this was noticed in the logs:{code}LOG: duration: 3.734 ms execute : DELETE FROM environments WHERE ID NOT IN (SELECT environment_id FROM catalogs WHERE environment_id IS NOT NULLUNION SELECT environment_id FROM reportsWHERE environment_id IS NOT NULLUNION SELECT environment_id FROM factsetsWHERE environment_id IS NOT NULL)LOG: temporary file: path "pg_tblspc/16400/PG_11_...", size 127286260{code}This ticket's a reminder to evaluate whether that's actually the query we want, e.g. {{ union }} vs {{ union all }} , etc.
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails
Jira (PDB-5495) Investigate observed slow/expensive environment gc query
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5495 Investigate observed slow/expensive environment gc query Issue Type: Task Assignee: Unassigned Components: PuppetDB Created: 2022/05/10 9:20 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet
Jira (PDB-5484) Check the code via clj-kondo (linter)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5484 Check the code via clj-kondo (linter) Change By: Rob Browning Team: HA Dumpling Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.444044.1650299798000.24034.1651682340064%40Atlassian.JIRA.
Jira (PDB-5486) Investigate making CI more similar to PE's [spike]
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-5486 Investigate making CI more similar to PE's [spike] Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.444745.1650905233000.17179.1650905280157%40Atlassian.JIRA.
Jira (PDB-5486) Investigate making CI more similar to PE's [spike]
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5486 Investigate making CI more similar to PE's [spike] Issue Type: Task Assignee: Unassigned Created: 2022/04/25 9:47 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.4447
Jira (PDB-5482) Log query PQL text (when available) when log-queries is true
Title: Message Title Rob Browning assigned an issue to Stel Abrego PuppetDB / PDB-5482 Log query PQL text (when available) when log-queries is true Change By: Rob Browning Assignee: Rob Browning Stel Abrego Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.443535.1649866678000.17176.1650905040237%40Atlassian.JIRA.
Jira (PDB-5485) Move to github actions
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-5485 Move to github actions Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.444744.1650904924000.17177.1650905040284%40Atlassian.JIRA.
Jira (PDB-5482) Log query PQL text (when available) when log-queries is true
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-5482 Log query PQL text (when available) when log-queries is true Change By: Rob Browning Assignee: Stel Abrego Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.443535.1649866678000.17172.1650904980158%40Atlassian.JIRA.
Jira (PDB-5485) Move to github actions
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5485 Move to github actions Issue Type: Improvement Assignee: Unassigned Created: 2022/04/25 9:42 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.444744.1650904924000.1717
Jira (PDB-5484) Check the code via clj-kondo (linter)
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5484 Check the code via clj-kondo (linter) Issue Type: Improvement Assignee: Rob Browning Created: 2022/04/18 9:36 AM Priority: Normal Reporter: Rob Browning A trial showed that it found a number of relevant issues, so let's add it alongside eastwood. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
