On Tue, Mar 05, 2002 at 09:19:35AM -0700, Sasha Pachev wrote: > On Tuesday 05 March 2002 01:17 am, Jeremy Zawodny wrote: > > When the machine is pounding away on updates (over 300/sec), it can > > take a long time to get a response to SHOW SLAVE STATUS. ?I get one, > > but it can take between 5 and 30 seconds: > > My first inclination was to blame FreeBSD threads, but then I > decided I need to gather some more hard evidence before I could do > it. Is SHOW SLAVE STATUS the only command that is that slow when > this happens?
Yes. > Try SHOW PROCESSLIST, SHOW VARIABLES, SHOW STATUS, SHOW MASTER > STATUS. Tried all of them and they're fast. In other news, the server hit another duplicate key problem. This time I was able to do this: slave stop; set sql_slave_skip_counter = 1; slave start; And it worked! So the new code seems to be better in that respect. :-) 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.47-max: up 26 days, processed 894,010,106 queries (394/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
