What about using the skip-name-resolve option rather than skip-grant-tables? I'm using the 3.23.51 binaries, also, and would appreciate knowing if this makes a difference. Debian potato 2.95.2 is a known good compiler, too, isn't it Jeremy? I may have to recompile my own anyway to change ft_min_word_length.
On another note with 3.23.51, I'm getting these errors every 30 seconds in my slave error logs: ---------------------------- 020624 5:00:00 Slave: Failed reading log event, reconnecting to retry, log 'db1-bin.008' position 3112 020624 5:00:00 Slave: reconnected to master '[EMAIL PROTECTED]:3306',replication resumed in log 'db1-bin.008' at position 3112 020624 5:00:30 Error reading packet from server: (server_errno=1159) ---------------------------- Is this just a normal timeout I can ignore? I'm still developing, so there's no real activity on these machines, yet. Is there a timeout value I can adjust? It's just annoying to see my error log growing so much with no activity. Thanks, --jeff ----- Original Message ----- From: "Jeremy Zawodny" <[EMAIL PROTECTED]> To: "Steven Roussey" <[EMAIL PROTECTED]> Cc: "'Mysql'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, June 23, 2002 2:55 AM Subject: Re: Load problems with 3.23.51 > On Sat, Jun 22, 2002 at 05:25:59PM -0700, Steven Roussey wrote: > > Hi all, > > > > I have MySQL 3.23.47 running on our sever. I skipped 48 through 50 and > > tried 51. No dice. It does not handle load, CPU and the load average go > > through the roof. I'm using Red Hat Linux 7.2 and the official mysql > > binaries. It appears to be slow to connect, causing 0.5 to 1.0 second > > delay on connection. Using persistent connections from PHP does not make > > much of a difference. I thought it might be the hostname lookup changes > > so I chose skip-grant-tables. This doesn't actually skip the hostname > > lookup though and had no effect. > > > > Most queries are shorter than 1 second so this problem causes > > catastrophic problems by making queries last a multiple times longer, > > which make the number of concurrent queries jump exponentially. This is > > a bad thing. And sadly makes 3.23.51 unusable. > > > > Does anyone else note these types of issues? > > As another data point for you, I've got 3.23.51 running on our master > quite well. The difference is that I built it from source (to get a > critical InnoDB patch). I don't recall which compiler the MySQL folks > used (and which glibc), but my source build used Debian Woody's gcc > 2.95.4. > > That could have something to do with it... > > Jeremy > -- > Jeremy D. Zawodny, <[EMAIL PROTECTED]> > Technical Yahoo - Yahoo Finance > Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 > > MySQL 3.23.51: up 24 days, processed 523,371,775 queries (248/sec. avg) > > --------------------------------------------------------------------- > 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
