On Tuesday, August 12, 2014 5:58:34 PM UTC+2, Ramin K wrote: > > On 8/12/2014 8:54 AM, Ramin K wrote: > [...]
> > You could try dropping the table and recreating it, but it might orphan > > all the resources. If you want the longer safer way, this is how I've > > done it in the past. Note that you'll need to dump and import the data > > for that table in order to reclaim the space from the table. > > > > > https://ask.puppetlabs.com/question/884/how-do-i-reduce-the-space-mysql-is-using-for-puppet-dashboard/?answer=885#post-id-885 > > > I made an error. Because you're already using file per table the > optimize step will reclaim the space as long as you've already purged > the data. > > Ramin Thanks for the reply. I have reduced the number of daily puppet runs on all nodes from 8 to 2 in also in order to reduce the load. It looks like this is also affecting the locking error message that I got previously and the reports:prune:orphaned job seems to execute as it should (but very slowly). As growth of the resource_statuses table also has slowed down I think I will let the reports:prune:orphaned job just run and see If that solves the problem. If not I may try to drop the table. Erling -- 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/d4dbc1b3-ae58-443d-82cd-04e85d6b12f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
