Jira (PDB-4875) Add option to log PDBQuery correlation uuids in Postgres
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4875 Add option to log PDBQuery correlation uuids in Postgres Change By: Zachary Kent - In PDB-4834 we added a log-queries config option which logs the AST & SQL produced as a result of queries PDB receives. It may be useful to have a way to correlate these logs with those in Postgres. One way of accomplishing this would be to have Postgres log the PDB uuid used for a query. Then using the Postgres log line prefix created by %c we could more easily correlate any logging on the Postgres side with those generated in PDB. - - [Read here|https://www.postgresql.org/docs/11/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHAT] for more background on log_line_prefix in postgres. - - In the PDB code we would need to run `select pdb-uuid;` or a similar statement using the same connection as the SQL query to trigger postgres to log the PDB uuid with the %c id Postgres will add as a log line prefix. This would need to happen in [query_eng.clj/stream-query-result|https://github.com/puppetlabs/puppetdb/blob/master/src/puppetlabs/puppetdb/query_eng.clj#L210] and in [query_eng.clj/produce-streaming-body|https://github.com/puppetlabs/puppetdb/blob/master/src/puppetlabs/puppetdb/query_eng.clj#L280]. Notice in the 2nd link how we would need to do this in the inner `with-transacted-connection` form. This is due to PDB currently using two hikari connections per query as explained in PDB-4871. If this ticket is resolved you won't need to worry about the nested transactions using different connections. - Add Comment
Jira (PDB-4875) Add option to log PDBQuery correlation uuids in Postgres
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4875 Add option to log PDBQuery correlation uuids in Postgres Change By: Zachary Kent - In PDB-4834 we added a log-queries config option which logs the AST & SQL produced as a result of queries PDB receives. It may be useful to have a way to correlate these logs with those in Postgres. One way of accomplishing this would be to have Postgres log the PDB uuid used for a query. Then using the Postgres log line prefix created by %c we could more easily correlate any logging on the Postgres side with those generated in PDB. - - [Read here|https://www.postgresql.org/docs/11/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHAT] for more background on log_line_prefix in postgres. - - In the PDB code we would need to run `select pdb-uuid;` or a similar statement using the same connection as the SQL query to trigger postgres to log the PDB uuid with the %c id Postgres will add as a log line prefix. This would need to happen in [query_eng.clj/stream-query-result|https://github.com/puppetlabs/puppetdb/blob/master/src/puppetlabs/puppetdb/query_eng.clj#L210] and in [query_eng.clj/produce-streaming-body|https://github.com/puppetlabs/puppetdb/blob/master/src/puppetlabs/puppetdb/query_eng.clj#L280]. Notice in the 2nd link how we would need to do this in the inner `with-transacted-connection` form. This is due to PDB currently using two hikari connections per query as explained in PDB-4871. If this ticket is resolved you won't need to worry about the nested transactions using different connections. - Add Comment
Jira (PDB-3635) Add ability to disable storage of resource events
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3635 Add ability to disable storage of resource events Change By: Zachary Kent Labels: tsr-pdb-backlog Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.203773.1501712836000.136392.1612831080042%40Atlassian.JIRA.
Jira (PDB-4268) Add some kind of metric tracking the number of concurrent enqueues
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4268 Add some kind of metric tracking the number of concurrent enqueues Change By: Zachary Kent Acceptance Criteria: * An added metric to the mq-metrics-registry which tracks the number of commands waiting to acquire a token from the write semaphore at any given time. * A test which shows that this metric increases and decreases as expected. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.296417.1550251531000.136347.1612829820092%40Atlassian.JIRA.
Jira (PDB-3635) Add ability to disable storage of resource events
Title: Message Title Austin Blatt commented on PDB-3635 Re: Add ability to disable storage of resource events It is important to ensure that the report hash is stable, for PE puppetdb's sync to work correctly, the hash of the report we store initially must be equal to the hash of the report that we sync. I don't anticipate any issues with this as events are not included in the report hash https://github.com/puppetlabs/puppetdb/blob/6b4cf67b7af9b1fa0051c3b0b148788358f117e4/src/puppetlabs/puppetdb/scf/hash.clj#L188-L196 but it is important to keep in mind. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.203773.1501712836000.136346.1612829820041%40Atlassian.JIRA.
Jira (PDB-3635) Add ability to disable storage of resource events
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-3635 Add ability to disable storage of resource events Change By: Austin Blatt Acceptance Criteria: - When resource-events-ttl is set to zero, resource-events are not stored in the resource events postgres - resource events are not included in the map that is used to make the hash for the resource events pdb-ext- A test showing that when syncing a report submitted with resource events it syncs to the other PuppetDB and creates a report with the same hash Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.203773.1501712836000.136339.1612829520110%40Atlassian.JIRA.
Jira (PDB-3635) Add ability to disable storage of resource events
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-3635 Add ability to disable storage of resource events Change By: Austin Blatt Acceptance Criteria: - When resource-events-ttl is set to zero, resource-events are not stored in the resource events- resource events are not included in the map that is used to make the hash for the resource eventspdb-ext- A test showing that when syncing a report submitted with resource events it syncs to the other PuppetDB and creates a report with the same hash Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.203773.1501712836000.136338.1612829520050%40Atlassian.JIRA.
Jira (PDB-4524) Provide way to stop/start command processing (maybe only internal initially)
Title: Message Title Zachary Kent commented on PDB-4524 Re: Provide way to stop/start command processing (maybe only internal initially) After discussing this a bit with Rob Browning there were two other approaches he suggested which would eliminate the need to poll the atom in the dochan loop described above. 1) We could use an empty java object created with the call: (Object.) We would store this object in the app context as a coordination mechanism between the dochan loop and the TK method to stop command processing. In the dochan loop it would attempt to lock the object with: (.lock obj-name) before pulling a command off of the queue. This would allow the TK method that's added to lock the object the dochan loop checks when called. Doing this would cause the dochan loop to block waiting on the TK method to release the lock, blocking commands from being processed. 2) It's possible the that the Executor created in the GatedThreadpool defrecord. Has the ability to pause incoming tasks. We haven't looked through the docs in detail but it would be worth checking out before going with option 1 to see if this is possible. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.327600.1569963418000.136234.1612826220039%40Atlassian.JIRA.
Jira (PDB-4268) Add some kind of metric tracking the number of concurrent enqueues
Title: Message Title Zachary Kent commented on PDB-4268 Re: Add some kind of metric tracking the number of concurrent enqueues See related slack conversation here for more detail on what the approach described above will be measuring. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.296417.1550251531000.136215.1612824900031%40Atlassian.JIRA.
Jira (PDB-2420) Sync core retains the local query result seq head
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-2420 Sync core retains the local query result seq head Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: PuppetDB should synchronize with another instance more efficiently now. Previously it would synchronize each entity (factsets, reports, etc.) incrementally, holding open PostgreSQL queries/transactions throughout the entire process, which could take a long time. Those transactions could substantially harm database performance, increase table fragmentation, and if entangled with something like pglogical, increase transient storage requirements (by blocking WAL log reclaimaton). Now instead, the queries should completed up-front, as quickly as possible. Team: HA Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10853) When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact
Title: Message Title Shaigy Nixon commented on PUP-10853 Re: When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact Thank you Josh Cooper. We will target the PE change for next release Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383136.1610563179000.136110.1612820760043%40Atlassian.JIRA.
Jira (PDB-4986) Instrument pdb to capture details when sync or shutdown hangs
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4986 Instrument pdb to capture details when sync or shutdown hangs Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: Some additional diagnostic information should now be logged (including backtraces from relevant threads) if the shutdown process cannot finish in a timely fashion. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.380573.1607557653000.136108.1612820700082%40Atlassian.JIRA.
Jira (PDB-4974) Wait on schedulers to shut down
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4974 Wait on schedulers to shut down Change By: Rob Browning Release Notes: Bug Fix Release Notes Summary: Previously an attempt to stop (or restart) PuppetDB might appear to succeed, even though some of its components were actually still running. That's because PuppetDB wasn't actually waiting for some of the internal tasks to finish as had been expected. Now PuppetDB should block during stop or restart until all of the components have actually shut down. This issue is a likely contributor to some cases where PuppetDB appeared to restart/reload successfully, but sync never started working again. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (PUP-10856) Slower puppet agent run after agent upgrade to version 6
Title: Message Title Gheorghe Popescu commented on PUP-10856 Re: Slower puppet agent run after agent upgrade to version 6 Ashok Mahajan the releases are planned for this week. Most likely the packages will be available on 10th feb. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383327.1610697413000.135594.1612802940136%40Atlassian.JIRA.
Jira (PUP-10856) Slower puppet agent run after agent upgrade to version 6
Title: Message Title Ashok Mahajan commented on PUP-10856 Re: Slower puppet agent run after agent upgrade to version 6 Gheorghe Popescu : Any tentative/approximate date for the release of these version ? Thank you. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383327.1610697413000.135561.1612802100078%40Atlassian.JIRA.
Jira (FACT-2935) Extend Facter 3 API with resolve
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-2935 Extend Facter 3 API with resolve Change By: Gabriel Nagy Assignee: Gabriel Nagy Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.385954.1612344499000.135505.1612799640128%40Atlassian.JIRA.
Jira (PDB-4268) Add some kind of metric tracking the number of concurrent enqueues
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-4268 Add some kind of metric tracking the number of concurrent enqueues Change By: Bogdan Irimie Team: PuppetDB Ghost Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.296417.1550251531000.135485.1612798740050%40Atlassian.JIRA.
Jira (PDB-4524) Provide way to stop/start command processing (maybe only internal initially)
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-4524 Provide way to stop/start command processing (maybe only internal initially) Change By: Bogdan Irimie Acceptance Criteria: * A new TK service method which allows the toggling of command processing, this should be possible from both the FOSS pdb repo and from the pdbext repo * A test which shows that command processing can be halted by using this TK service method Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.327600.1569963418000.135472.1612797720107%40Atlassian.JIRA.
Jira (PDB-4524) Provide way to stop/start command processing (maybe only internal initially)
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-4524 Provide way to stop/start command processing (maybe only internal initially) Change By: Bogdan Irimie Acceptance Criteria: * A new TK service method which allows the toggling of command processing, this should be possible from both the FOSS pdb repo and from the pdbext repo * A test which shows that command processing can be halted by using this TK service method Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.327600.1569963418000.135471.1612797720064%40Atlassian.JIRA.
Jira (PUP-10893) Update Public-facing Puppet docs to include OSX 11 Big Sur
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-10893 Update Public-facing Puppet docs to include OSX 11 Big Sur Issue Type: Task Assignee: Unassigned Created: 2021/02/08 7:04 AM Priority: Normal Reporter: Mihai Buzgau Update Public-facing Puppet docs to include this platform Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10893) Update Public-facing Puppet docs to include OSX 11 Big Sur
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10893 Update Public-facing Puppet docs to include OSX 11 Big Sur Change By: Mihai Buzgau Epic Link: PA-3612 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.386622.1612796673000.135447.1612796700098%40Atlassian.JIRA.
Jira (PUP-10878) Prepare release announcement (Puppet Platform 7.4.0)
Title: Message Title Claire Cadman commented on PUP-10878 Re: Prepare release announcement (Puppet Platform 7.4.0) Nirupama Mantha Mihai Buzgau Here is an email draft and list of the 7.4 release notes: https://docs.google.com/document/d/1jttwqo-uQwIt3yFQYsa7hs_SwFp-SZls_tSATgD9AvM/edit Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.385571.1611965954000.135398.1612794240073%40Atlassian.JIRA.
Jira (PUP-10868) Prepare release announcement (Puppet Platform 6.21.0)
Title: Message Title Claire Cadman commented on PUP-10868 Re: Prepare release announcement (Puppet Platform 6.21.0) Nirupama Mantha Mihai Buzgau Here is an email draft and list of the release notes: https://docs.google.com/document/d/1AwYUpitXFsKO8A25g9Bc1b10uEfZ8VOv3L2NN-Oq2Gs/edit Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.385535.1611965558000.135395.1612794120187%40Atlassian.JIRA.
Jira (PUP-10892) Update Public-facing Puppet docs to include Fedora 33 x86_64
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10892 Update Public-facing Puppet docs to include Fedora 33 x86_64 Change By: Mihai Buzgau Epic Link: PA-3600 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.386584.1612776588000.135243.1612776600177%40Atlassian.JIRA.
Jira (PUP-10892) Update Public-facing Puppet docs to include Fedora 33 x86_64
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-10892 Update Public-facing Puppet docs to include Fedora 33 x86_64 Issue Type: Task Assignee: Unassigned Created: 2021/02/08 1:29 AM Priority: Normal Reporter: Mihai Buzgau Update Public-facing Puppet docs to include this platform Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10891) Update Public-facing Puppet docs to include RedHat 8 Power9
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10891 Update Public-facing Puppet docs to include RedHat 8 Power9 Change By: Mihai Buzgau Epic Link: PA-3587 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.386554.1612775622000.135237.1612775640108%40Atlassian.JIRA.
Jira (PUP-10891) Update Public-facing Puppet docs to include RedHat 8 Power9
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-10891 Update Public-facing Puppet docs to include RedHat 8 Power9 Issue Type: Task Assignee: Unassigned Created: 2021/02/08 1:13 AM Priority: Normal Reporter: Mihai Buzgau Update Public-facing Puppet docs to include this platform Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10856) Slower puppet agent run after agent upgrade to version 6
Title: Message Title Gheorghe Popescu commented on PUP-10856 Re: Slower puppet agent run after agent upgrade to version 6 Ashok Mahajan the fix will be available in the 6.21.0 and 7.4.0 versions. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383327.1610697413000.135218.1612771200184%40Atlassian.JIRA.
