I''m using puppet-dashboard 1.1.0-1 on Ubuntu. I remove old reports using this command: nice -n +1 rake RAILS_ENV=production reports:prune upto=1 unit=mon This seems to work fine, and the amount of reports returnd by this mysql query seems to drop by the proper amount: select count(*) from reports; Right now it returns a value of 12591. So far so good. The problem is the resource_statuses statuses table. Right now I have 63695 distinct values for report_id as returned by: select count(*) from (select distinct report_id from resource_statuses)as count; Am I missing something? It seems to me this can be fixed by just making the table "cascade on delete", though I''ll freely admit I have only enough ruby experience to get a little ways past Hello World. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Rob Braden
2011-Jul-12 14:19 UTC
[Puppet Users] Re: Possible leaking records in dashboard db
There is already a bug open on this issue: http://projects.puppetlabs.com/issues/6717 So far, I''ve been manually cleaning out tables periodically, but that''s not going to work long term. On Jul 12, 1:17 am, Patrick <kc7...@gmail.com> wrote:> I''m using puppet-dashboard 1.1.0-1 on Ubuntu. I remove old reports using this command: > nice -n +1 rake RAILS_ENV=production reports:prune upto=1 unit=mon > > This seems to work fine, and the amount of reports returnd by this mysql query seems to drop by the proper amount: > select count(*) from reports; > > Right now it returns a value of 12591. So far so good. > > The problem is the resource_statuses statuses table. Right now I have 63695 distinct values for report_id as returned by: > select count(*) from (select distinct report_id from resource_statuses)as count; > > Am I missing something? > > It seems to me this can be fixed by just making the table "cascade on delete", though I''ll freely admit I have only enough ruby experience to get a little ways past Hello World.-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.