We recently got an snmp trap event storm from a firewall that dropped 1000 events in the status table. Mysql spun up to 99% on one of the CPUs on the server. The mysql 'show processlist' statement showed that zenoss was constantly doing a "DELETE FROM STATUS WHERE clearid IS NOT NULL" resulting in a full table scan of the status table.
Adding an index on status.clearid immediately dropped mysql cpu usage down from 99% to a normal 1-8%. I have verified this by removing the index and watching mysql jump back to 99%. To add the index: ALTER TABLE status ADD INDEX clearid_idx (clearid). Hope this helps. ------------------------ AJ -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=5670#5670 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
