Bug #56737 Slow retrieve of information when GW not available
Submitted: 12 Sep 2010 15:59 Modified: 9 Jan 2015 16:41
Reporter: Jorge Bastos Email Updates:
Status: No Feedback Impact on me:
None 
Category:Connector / NET Severity:S2 (Serious)
Version:6.3.4 OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[12 Sep 2010 15:59] Jorge Bastos
Description:
Howdy,

With MySQL server installed on a machine, whether Win or Linux/unix, when the GW defined on that machine is unacessible, the access to MySQL is extremely slow.
I have the MySQL server defined on the [mysqld] section with:

skip-name-resolve

so that it doesn't make any reverse DNS lookup's.

Is there a reason to when the GW defines on the machine where MySQL server is installed, is not accessible make the access to MySQL slow?

How to repeat:
* Install a MySQL server on a machine
* define a non-existing GW for the machine
[22 Sep 2010 11:34] Jorge Bastos
Howdy,

Any news about this?
[22 Oct 2010 20:37] Reggie Burnett
how does the mysql command line client respond?  Is it quick on the same box that c/net is slow?
[23 Nov 2010 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[10 Dec 2011 21:42] Jorge Bastos
Howdy,
Getting back to this.

In the commandline it works with the normal speed.