Hello. https://secure.opsera.com/jira/browse/OPS-950
I'm using Opsview v 3.3.2 now. but i think there is no service_saved_state table(in our DB, its size is 220MB) growing problem. ( i executed the DELETE query which you pasted but there is no change in table data length size. ) i doubt it is the main cause of performance degradation. 2010/1/18 Ton Voon <[email protected]> > Hi! > > Just wanted to make people aware of a fix for reducing the time to run > import_runtime. This affects people if there are importing into ODW and have > a large number of services. > > The cleanup section wasn't getting invoked correctly which means that the > odw.service_saved_state table will continue to grow and it may slow down the > duration of the hourly imports into ODW. > > You can run this SQL command on your ODW database if you find that the > odw.service_saved_state table is too large: > > mysql> DELETE FROM service_saved_state WHERE opsview_instance_id = 1 AND > start_timev <= UNIX_TIMESTAMP(NOW() - INTERVAL 7 DAY) > > The patch is here: > > > https://secure.opsera.com/wsvn/wsvn/opsview/trunk/opsview-core/bin/import_runtime?op=diff&; > > This will be included in a future release. > > Ton > > _______________________________________________ > Opsview-users mailing list > [email protected] > http://lists.opsview.org/lists/listinfo/opsview-users >
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
