Besides all the answers already provided by others, there might be also another reason for the fast growing database. This is the table 'resource_statuses' inside dashboard's database which is not purged by the rake script (at least not in Puppet 2.6.6 and 2.6.12). Patching the rake script will dramatically reduce the overall database size. I've provided more details here: http://berndadamowicz.wordpress.com/2011/12/07/keeping-puppet-dashboards-database-small/
Bernd Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im Auftrag von Jo Rhett Gesendet: Montag, 9. Januar 2012 19:40 An: Puppet Users Betreff: [Puppet Users] scaling projections for dashboard 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 : consonant endings by net philanthropy, open source and other randomness -- 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<mailto:puppet-users@googlegroups.com>. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com<mailto:puppet-users+unsubscr...@googlegroups.com>. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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.
