I've "inherited" the administration of a puppet-dashboard (version
1.1.0, installed on RHEL 5.6 from puppetlabs RPM), and have hit a
problem I'm hoping for some help with.
In short, one table, "resource_statuses" appears to be growing at a
rate far higher then the other tables:
mysql> select count(*) from nodes;
+----------+
| count(*) |
+----------+
| 107 |
+----------+
mysql> select count(*) from resource_statuses;
+-----------+
| count(*) |
+-----------+
| 188068011 |
+-----------+
Yeah, that's over 188 million rows. Currently, the entire mysql data
directory for the dashboard database is taking up 51 GB; the
resource_statuses.MYD file is 47 GB of that.
We've got a weekly cron job that runs "/usr/share/puppet-dashboard/
Rakefile RAILS_ENV=production reports:prune upto=2 unit=wk", and I've
run it manually, but it doesn't seem to impact that table.
Is there a "safe" way to reduce the number of rows in that table, and
limit it to keeping either X number of rows, or rows going back only
to a specific timespan (like, 2 weeks)?
Thanks in advance!
-- Sandy
--
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.
