It was probably attempting to do a reverse and nothing exists, so it just has to timeout.
Donny > -----Original Message----- > From: Frank Febbraro [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 07, 2004 3:23 PM > To: Donny Simonton; [EMAIL PROTECTED] > Subject: Re: MySQL 4.1.7 Network slowdown > > > I've been using mysql 4.1 since the first day it was out; it's all been > > trial and error. If I remember correctly, I found it on 4.1.0 when I > was > > doing a processlist, and noticed that some of the boxes connecting to > mysql > > had reverse and others didn't. So now we actually go to the /etc/hosts > file > > and name all of our boxes something just in the hosts file so it will be > > easier to know exactly what everything is. > > > > You might still want to file that as a bug and you can at least have > mysql > > determine if it's a bug or not. They will probably say it's on some > > documentation like on page 13,645 paragraph 12 or something so they > won't > > consider it a bug. But at least this way somebody else may know about > the > > problem. > > So do you think the 5+ second delay was that it was actually getting a > reverse lookup, just from somewhere that responded really slow, or it > tried, got some timeout, then gave up? > > Thanks again...so happy. > Frank > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
