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. 

ALTER TABLE report_logs ENGINE=InnoDB;

Then you can run the following and you'll see that there is in fact a new 
ibd file. 
ls -lah /var/lib/mysql/dashboard/report*
-rw-rw----. 1 mysql mysql 8.7K Oct 16 09:36 
/var/lib/mysql/dashboard/report_logs.frm
-rw-rw----. 1 mysql mysql  36M Oct 16 09:40 
/var/lib/mysql/dashboard/report_logs.ibd

So I don't think you have actually nuke your mysql configuration 
altogether. 

mjr

On Wednesday, October 15, 2014 3:32:26 PM UTC-4, Ramin K wrote:
>
> On 10/15/14 9:11 AM, Mark Rosedale wrote: 
> > Hello, 
> > 
> > I'm running puppet  with puppetdb and puppet-dashboard all on my master. 
> > 
> > I want to make sure that I don't get overrun with disk usage by either 
> > the master (storing reports) or the dbs for puppetdb (I'm running 
> > postgres) or puppet-dashboard (mysql). 
> > 
> > I'm wondering what some people do to manage disk usage for each of 
> these? 
>
> In regards to Puppet Dashboard, the Mysql based one, I wrote this up 
> over a year ago 
>
> https://ask.puppetlabs.com/question/884/how-do-i-reduce-the-space-mysql-is-using-for-puppet-dashboard/
>  
>
> Remember just doing the prunes will not reclaim space. You must optimize 
> the table in order to shrink it. And running the optimize will not 
> reclaim space unless the table resides in its own file. 
>
> 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/32f09a1e-94c7-471b-8681-e79f80312cc9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to