Does this happen across all nodes? This is an indication you might have a resource that affects a large set of nodes that suddenly changes every 4 days.
In the catalogs table, the 'hash' is just a hash of the catalogue data, if anything in the catalogue changes - it changes. And new entries are created. The database garbage collection is there to remove the orphaned entries. So really one could consider this part of normal operation, if your catalogues are constantly changing then the garbage collection runs are bigger. Did you see this happen on Sunday? On Fri, Jan 18, 2013 at 12:28 AM, Chuck <cssc...@gmail.com> wrote: > This is unconfirmed at this point. > > It seems like every 4 days starting Jan 4. 2013 (interesting is started in > 2013 and never happened in 2012) like the Catalog or Resource Hash changes, > causing the entire catalog_resource table to insert new entries, then > possibly GC deletes the old entries. > > If this holds true we will see this behavior again on Jan. 20, 2013. > Hopefully we will have a better idea of what is going on. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/APtEGbv578QJ. > > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
