Puppet users - Aug 2014 - Very large resource_statuses. reports:prune:orphaned fails with Mysql error

Hi!

I use Puppet enterprise 2.7.2. In the database for Puppet Dashboard
the resource_statuses table has grown rapidly the past month (when I was on 
vacation).
I have experienced this earlier also and have implemented the suggested 
solution
here: https://projects.puppetlabs.com/issues/6717
(downloaded a new rake task reports:prune:orphaned).
I have sucessfully executed that task in the past, but now it fails with an 
error:
Mysql::Error: Lock wait timeout exceeded; try restarting transaction: 
delete from resource_statuses where report_id not in (select id from 
reports) limit 1000.

The resource_statuses.ibd file is 103 GB! (containing about 250 million 
rows).
When this happened earlier the rake task reports:prune:orphaned ran for 
many days, but eventually completed. 

Is it possible to quickly drop the whole resource_statuses table and 
recreate it?

Note that I also currently work with upgrade / migration to Puppet 
Enterprise 
3.x but need to maintain this 2.7.2 installation in paralell.

Best regards,

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+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/f87939b4-61b1-4837-8969-07cf9022a552%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.