I'm not sure if this will help you, but it might: http://jeremy.zawodny.com/blog/archives/000173.html
(brief excerpt) "So the moral of the story is this: If you have a busy server that's getting a lot of quick connections, set your thread cache high enough that the Threads_created value in SHOW STATUS stops increasing. Your CPU will thank you." The only other thing I can think of is if you have a lock on the table (if it's MyISAM) at the same time, so the select is denied. Updates have preference in MySQL over reads when there's a lock, so a read query would wait for a write query. But then you'd get a timeout error. . .. SHOW STATUS LIKE 'Table%'; will show you the lock contention, if there is any. What else is going on in the database? Are you doing maintenance, like OPTIMIZE TABLE? That is a very odd situation. -Sheeri On 10/28/05, Johannes B. Ullrich <[EMAIL PROTECTED]> wrote: > sheeri kritzer wrote: > > What is max_connections set to (my.cnf?)? How many connections are > > there at a time? (show processlist) That would result in a "too many > > connections" error, but it's worth a shot. > > Max connections: 2000 > typically 10-20 used (hardly ever >100). > > > What is the thread cache set to? > > | thread_cache_size | 0 | > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
