search for: innodb_file_per_table

I am using Ubuntu 10.04 and ruby-enterprise (not ubuntu ruby) and installed puppet via gem. How can I install puppet-dashboard if I don''t see a gem available and if I use the ubuntu package, i get the whole slop of ruby packages sucked in (which i am trying to avoid)? # dpkg -i puppet-dashboard_1.1.0-1_all.deb Selecting previously deselected package puppet-dashboard. (Reading database

So I got dashboard up and running on our production system on Thursday before I left. Within 48 hours it had completed filled the /var filesystem. The ibdata1 file is currently at 8GB in size. 1. What size should I expect for ~500 nodes reporting every 30 minutes? 2. Are there some database cleanup scripts which I have managed to overlook that need to be run? -- Jo Rhett Net Consonance :

...buffer_size = 8M read_rnd_buffer_size = 2M bulk_insert_buffer_size = 16M myisam_sort_buffer_size = 64M myisam_max_sort_file_size = 10G myisam_max_extra_sort_file_size = 10G myisam_repair_threads = 1 myisam_recover # ***************************** INNODB Specific options **************************** innodb_file_per_table innodb_additional_mem_pool_size = 16M innodb_buffer_pool_size = 2048M innodb_data_home_dir = /data/mysqldata3/innodb_ts innodb_data_file_path = ibdata1:256M:autoextend innodb_file_io_threads = 4 innodb_thread_concurrency = 0 innodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size = 8M innodb_log_...

Hello, I have another quick one about puppet dashboard. We are using the Debian one for Squeeze (1.0.4) and as the database has significantly grown, if/when we click on a list of unresponsive nodes to check them, the web interface sits there doing nothing then the puppetmaster process starts timing out for all nodes compiling their catalogs. Has anyone got a workaround for this? Does it involve