On Thu, 11 Aug 2011 08:36:41 -0700 (PDT) Luke Bigum wrote: > Hi Arnau, Hi Luke, > This is not a Puppet Dashboard problem, it's a MySQL "feature" of > InnoDB. You're using per-table InnoDB data files. InnoDB data files > grow. They never, ever, ever shrink. So what you've got there is a > 22GB sparse file that MySQL will fill up with more resource_statuses > rows. It won't use that space for any other table because you've for > per-table InnoDB data files configured on.
You're right!! > I *think* one solution is to convert the resource_statuses to MyISAM > then back to InnoDB again but I've never done it. Another way is to > dump the database out, blow away the InnoDB data files and import the > dump (see > http://dev.mysql.com/doc/refman/5.5/en/innodb-data-log-reconfiguration.html). I'll try to do so. > Hope that helps, it does. > -Luke Cheers, Arnau -- 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.
