In rails ,Mysql.real_connect takes like 3 mins for every request when the mysql server is shut down

I am trying to render few static pages in my rails app when the mysql server is shut down. I tried to catch the Mysql::Error exception and render the corresponding static page for each controller.

When we just stop the mysql service in the machine where the mysql is installed. The Mysql::Error exception is thrown immediately and i am able to render the pages without any delay. but if i just shut down the server. The whole website becomes irresponsive.

I traced down the actual function in the rails framework , which is taking 3 mins 开发者_如何学Goto complete. It was this statement

Mysql.real_connect

in the active_record gem. which takes so long. Is there any way i can give a time out so that , when the mysql server is powered off. it returns with the Mysql::Error exception really quickly so that i can render the pages without any delay??

This is probably coming from the socket timeout within the mysql adapter. When the service is stopped, the server will respond quickly with a connection refused error. When the server itself is down, the socket will have to get a connection timeout before it returns. What you'll probably have to do is monkey patch the #real_connect method so that it first validates that the server is running by attempting a socket connection (with a timeout) before continuing on with the original implementation. This question may be of some help to you there:

How do I set the socket timeout in Ruby?

  dbh = Mysql.init
  dbh.options(Mysql::OPT_CONNECT_TIMEOUT, 6)