From: Yves M. <yme...@li...> - 2004-09-29 07:42:51
|
I found something about that when I ran out of space. I made a mistake an= d lost all my data (my fault). But if you try it and if you are not as stupid as me, it= can work :) 1/ dump your database somewhere 2/ drop the database and recreate it 3/ restore the data If you are using innoDB, this is the only way to reduce the size of the m= ysql files. I don't remember where I read that, but if you have no other solution, tr= y it and tell us :) About my mistake : I did 1/ 2/ 1/ instead of 1/ 2/ 3/ so I overwrote my d= ump with empty data :) Yves > Hi all, > > I sent an email to the list about a month ago on this issue and haven't > gotten a response. > > I have perfparse and am tracking about 80 servers and about 10 or so > monitors per server, all running at five minute intervals. I have 30 d= ays > worth of data in the database. > > Currently the perfdata_service_raw table is 45M rows and over 800M. Th= e > perfdata_service_bin table is 62M rows and about 1.6G (this is due to n= ot > purging for a long time before I got the deletion policies working, I t= hink > its about 900M of actual data). > > Due to the number of rows the perfparse-db-purge actually crashes mysql= due > to running out of buffer space... I have upped this to 16M and it still > crashes. > > I'd also like to be able to monitor trends in services over a longer pe= riod > of time, like say the last month, the last year, the last 5 years simil= ar to > the way mrtg does, but with the dataset the way it is that is currently= not > feasible. > > How much data are other people retaining? Has anyone else run into sim= ilar > issues? Does anyone have a solution? > > Thanks, > James > --=20 - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - - GPG key - http://ymettier.free.fr/gpg.txt - - Maitretarot - http://www.nongnu.org/maitretarot/ - - GTKtalog - http://www.nongnu.org/gtktalog/ - |