On 10/16/2014 6:51 AM, Mark Rosedale wrote:
I went through your ask post. This was extremely helpful information.
However, I wanted to add some updated information about reclaiming your
space the hard way.
According to the mysql documentation
<http://dev.mysql.com/doc/refman/5.6/en/tablespace-enabling.html> you
can change the innodb_file_per_table setting and then run the following
command to split the table off into its own file.
I wasn't aware that it was that easy to break tables out. That appears
to be a 5.5+ feature based on docs, but maybe I just can't find the
reference to it in earlier versions. At first glance this looked like a
very simple way to solve the problem. However it will reclaim space in
the manner you're expecting. The problem is that space in the system
idbata files is never reclaimed. If you've allowed your Dashboard db to
grow to 80GB without innodb_file_per_table when you create the new table
with this method the new table will be the size of the data which is
what we expect because it was created new. Unfortunately the system
ibdata files will still be 80GB.
http://dev.mysql.com/doc/refman/5.6/en/glossary.html#glos_system_tablespace
Ramin
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5442DE70.7000008%40badapple.net.
For more options, visit https://groups.google.com/d/optout.
