Thanks Wyatt, I dropped it a while back after realizing how easy this was. All is back now, and metrics are returning to normal. The large facts are now gone and so are our issues. :-) I was wrong on the GC, it's at the default of one hour. I was thinking node-ttl, which we set to 1 week. Thanks again, case closed.
On Tuesday, April 26, 2016 at 3:49:13 PM UTC-5, Wyatt Alt wrote: > > Mike, > > If you have no issue dropping and recreating the full database, that's > totally a workaround here (you know your requirements better than I, so > please don't take this as an endorsement of the approach :-) ). > > To do this just stop PuppetDB, drop the puppetdb database, and recreate > the database with the options you want (the usual ones are described > here, but some people use different: > https://docs.puppet.com/puppetdb/latest/configure.html#using-postgresql), > and restart PuppetDB. > > PuppetDB won't recreate the database for you but once that's in place > it'll create the tables/indices on startup. You may also consider > setting gc-interval to something less than 1 week, unless there's a good > reason for it being so long. A one-week interval will allow a lot of > time for bloat to build up. > > Wyatt > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ef981bb8-6615-43fb-887b-ab3e2547a45b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
