There's a couple of issues that conspire to create your problem. First the ibdata1 file only grows and never shrinks even if you remove data. Also Zenoss doesn't purge the details table of old information automatically (dunno if this was fixed in 2.2). So you need to run a query like so, to do it.
Code: DELETE FROM detail WHERE evid NOT IN (SELECT evid FROM status UNION SELECT evid FROM history); By purging this old data this should cause the ibdata1 file to stabilize at a certain size. Your Option 3 would be to configure your innodb to use the option innodb_file_per_table. You'd still have to dump and reload your data to get it in the file_per_table space, but once there an optimize will cause the table files to shrink. I use option 3. :) -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=21079#21079 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
