Being an *NIX developer for longer than I care to recall and using Linux since .99r, I would disagree about a buggy io subsystem. There may be some issues with marshalling and /or threads (usually a coding/synchronization issue not a thread issue), but I would suspect it is relating to db caching. I would try committing the inserts to the drive by using the --flush parameter upon invocation of mysqld. I don't know what type of performance hit this may cause you, but I would suspect that all of your corruption issues would disappear.
Respectfully, Pat... BTW the only OS's that I have experience table corruption has been with MS (NT and 98) due to OS freezes and blue screens. --flush cured those. ----- Original Message ----- From: "Heikki Tuuri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 18, 2001 12:53 PM Subject: RE: Frequently corrupt tables > Hi! > > >Well, for one, I believe that Slashdot uses InnoDB tables, which tend to > handle > >a little better under very high load. > >Steve Meyers > > -----Original Message----- > >> From: Matthew Bloch [mailto:[EMAIL PROTECTED]] > >> Sent: Thursday, October 18, 2001 3:34 AM> To: [EMAIL PROTECTED] > >> Cc: Peter Taphouse; Alec O'Donnell > > Subject: Frequently corrupt tables > > > > >> Hello all; > > > >> I'm running several MySQL installation (all version 3.23.37 under Linux) > >> under what I presume are some fairly harsh conditions, and wondered what > >> circumstances cause tables to be corrupted and need fixing with myisamchk. > >> This is happening once every few days and it's becoming a pain. I have a > >> multithreaded process which is constantly opening and closing connections > >> to the database and trying to increase its concurrency until the load > >> average reaches something comfortable like 15, and the network connection > >> is saturated. I've had to throttle it back to stop it opening more than > >> 32 simultaenous DB connections but otherwise it works fine. Until I start > >> getting errors from the table handler, that is, and the whole thing grinds > >> to a halt until I fix the table manually. > > > >> Can anybody shed some light on this? I can't believe I'm putting it under > >> more load than something like Slashdot would, and they don't (appear to) > >> have half the troubles I've had. > > > cheers, > > > -- > >> Matthew > >http://www.soup-kitchen.net/ > > > > ICQ 19482073 > > There seem to be i/o bugs in Linux. What is > your Linux kernel version? 2.2.19 is believed > to be the most stable. > > My current hypothesis is that many disk drivers > in Linux are buggy. My development platform > 2.4.4 has been totally stable while another > computer with 2.2.14 expressed file read errors > and crashes. > > High load should not cause table corruption, > but it may make some bugs surface in the OS. > Actually, has anybody seen table corruption > on Win NT/2000 or Solaris? > > Regards, > > Heikki > http://www.innodb.com > > > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
