Mark Atwood wrote:
Invoking memories of professional services clients who were "enjoying"
assorted problems with MySQL's use of /tmp and of envvar TMPDIR..
I also strongly mislike MySQL's "trick" of creating a temp file,
opening it, and then unlinking it.
This makes it very hard for sysadmins to see what is going on,
answering the question "what is taking ALL the space in /tmp?".
And in a related problem, the error messages generated by MySQL when
the tmp space fills up are Not Helpful. This is a world of hurt that
Drizzle should do much better.
We recently picked up an SSD due to the 3 gig MySQL ramdisk (made in an
effort to eliminate a bit of disk I/O) tossing temp file errors that
never happened outside of the ramdisk:
100303 9:12:52 [ERROR] /usr/sbin/mysqld: Incorrect key file for table
'/var/lib/mysql/ramdisk/#sql_3c28_1.MYI'; try to repair it
100303 9:12:52 [ERROR] /usr/sbin/mysqld: Incorrect key file for table
'/var/lib/mysql/ramdisk/#sql_3c28_0.MYI'; try to repair it
Unfortunately, my theory that it has to do with the 3 gig ramdisk being
too small is only a theory. Because I can never catch that directory
holding actual files of any significance. It either appears empty or
has a handful of unlinked files that I can't get a proper size from.
Argh. Upping the size of the ramdisk reduced the quantity of these that
I see, and made it so the server didn't lock itself up.
--
Erik Jacobson
Server Administrator
Themis Media ( http://www.themis-media.com/ )
The Escapist ( http://www.escapistmagazine.com/ )
( Vim, Tabs, BSD Braces, Debian, and Perl )
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
