View Full Version : Solved When cache is deleted/optimized my /tmp directory fills and mysql crashes

09-09-11, 18:16
As the title says. I have to reboot mysql, which clears the tmp directory and empty the table that crashed. This only happens on the tables that are very large, like vbenterprisetranslator_cache_short_ru, which is over 3.3 million records and 500mb.

My cache ttl is 15 days. Should I make it shorter?

12-09-11, 11:14
Please take a look on this thread: http://www.vbenterprisetranslator.com/forum/vbet4-general-discussions/408-vbet-performance.html

12-09-11, 18:56
Right - I have all performance suggestions implemented. The question is; what can I do to prevent /tmp from running out of space when these tables are being optimized ('repair by sort' ) ?

13-09-11, 11:32
Ok, you should change your Cache clearing strategy, please find out which of them is the best for you, short description you can find there:

admincp-> vBet Cache -> Cache clearing strategy
It is not recomended to delete all cache data after TTL interval, try to use other strategy. Of course you can try to make ttl shorter, but i suggest you to, at first try out other clearing strategy. This should help, if not let us know

16-09-11, 17:31
Right - I have all performance suggestions implemented. The question is; what can I do to prevent /tmp from running out of space when these tables are being optimized ('repair by sort' ) ?

Just as Radek wrote you - you can use other clearing strategy. Making TTL shorter will degrade your performance, because more often your forum will ask for outside translation.
About /tmp folder - you can also ask MySQL support/forums about the issue. It is clearly our of vBET scope. We are ready for big forums and allow you to use different clearing strategies for faster cleanings on large boards. Still if your MySQL crashes this is MySQL issue. Or maybe it is your OS issue - please try to allow for bigger temporary files.

18-09-11, 15:19
I've actually tried different clearing strategies. The bottleneck is when a very large table is optimized after the deletion.

18-09-11, 19:02
I think I figured it out. My tmp directory was only 500mb. When a table close to 1gb was optimized it needed more space then that to do all the optimization. So instead of increasing the size of the tmp directory I created a new one that uses RAM instead of disk according to these instructions: themattreid.com/ wordpress/2011/04/04/mysql-and-ramdisk-or-how-to-make-tmpdir-usage-queries-faster/

Since a lot of larger queries make tmp files to execute this will speed up that process as well.

19-09-11, 12:04
To clarify, is this problem solved, for any other problems please open new threads

28-09-11, 07:41
No answer, we consider this problem solved, if you will have any question for this issue we will reopen it, for any other question please open new thread

AfrikaansAlbanianArabicBelarusianBulgarianCatalanChineseCroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrenchGalicianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKoreanLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishTaiwaneseThaiTurkishUkrainianVietnameseWelshYiddish
Languages translations delivered by vBET 4.9.99