PuppetDB 3.0.2 - August 4, 2015

PuppetDB 3.0.2 Downloads

------------------------

Available in native package format as part of Puppet Collection 1 (PC1).
More information on the PC1 repositories is available here:
http://bit.ly/1HQJDNb

Binary tarball: http://downloads.puppetlabs.com/puppetdb/

Source: http://github.com/puppetlabs/puppetdb

Please report feedback via the Puppet Labs tickets site, using an affected
PuppetDB version of 3.0.2: https://tickets.puppetlabs.com/browse/PDB

Documentation: http://docs.puppetlabs.com/puppetdb/3.0/

Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb

PuppetDB 3.0.2 Release Notes

----------------------------


PuppetDB 3.0.2 is a bugfix release to address performance issues with the
aggregate-event-count and fact-paths endpoints as well as memory starvation
involving structured-facts.


   -

   Previously PuppetDB cached prepared statements for SQL queries. This
   caused memory starvation involving structured-facts where large
   structured-facts would create a new prepared statement object for each
   update. The large objects would accumulate in the cache due to the non-zero
   cache size. This release addresses this issue in two ways, by disabling the
   cache and changing the structured-facts update queries to be more
   efficient. (https://tickets.puppetlabs.com/browse/PDB-1721)

   -

   Given a large number of nodes and reports, consumers of the
   aggregate-event-counts endpoint were experiencing slow response times.
   These performance issues have have been addressed in this release. One
   notable outcome from these fixes is that the endpoint no longer requires a
   query parameter. (https://tickets.puppetlabs.com/browse/PDB-1809)



   -

   Some PuppetDB tables were never analyzed by the autovacuum analyzer
   which led to performance issues with the fact-paths endpoint. This release
   adds code to perform the analyze whenever PuppetDB schema are updated. (
   https://tickets.puppetlabs.com/browse/PDB-1812)



   -

   This release fixes an issue where the `max-frame-size` parameter was
   being ignored by consumers of the command queue, causing large commands to
   produce stacktraces in the PuppetDB log. (
   https://tickets.puppetlabs.com/browse/PDB-1812)


Contributors
-----------

Andrew Roetker, Jorie Tappa, Ken Barber, Melissa Stone, Nick Fagerlund, Rob
Browning, Russell Mull, Wyatt Alt

Cheers,
PuppetDB Team

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAL56sG%3DLqGiCeosbF6yYzvUn4vxy6G1UPqT0eh5wVVKo-G1Xpg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to