MySQL resolve:FailoverDataConnector failover slow

[Ho, PeiQuan]

I meant to say when the master MySQL server is down, the transaction to the failover server works, but is extremely slow.

Thanks,
-PQ

From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Ho, PeiQuan
Sent: Tuesday, April 14, 2015 11:21 AM
To: users at shibboleth.net
Subject: MySQL resolve:FailoverDataConnector failover slow

Hi,

                We have a custom attribute that is sourced from a MySQL database.  We have a master and slave MySQL server and we are using the resolver:FailoverDataConnector item to handle failovers... something like this:

            <resolver:DataConnector id="configConnector" readOnlyConnection="true" noResultIsError="false" xsi:type="RelationalDatabase" xmlns="urn:mace:shibboleth:2.0:resolver:dc">

                <resolver:FailoverDataConnector ref="configFailoverConnector" />
.
.
  </resolver:DataConnector>

    <resolver:DataConnector id="configFailoverConnector" readOnlyConnection="true" noResultIsError="false" xsi:type="RelationalDatabase" xmlns="urn:mace:shibboleth:2.0:resolver:dc">
.
.
  </resolver:DataConnector>

During testing however, we noticed that when the master is done, the transaction is really slow.. way slower than the expected timeout values... and even after the authentication has succeeded, the IDP takes a long time before passing the session back to the SP... like minutes!  We're also using mysql connector string of the type below, but it still doesn't seem like timeout values are honored.
                jdbc:mysql://MYSQL_SERVER/DATABASE?connectTimeout=5000&amp;socketTimeout=5000

Does anyone have any ideas what might be wrong?

Thanks,
-PQ

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20150414/f48309fa/attachment-0001.html