[RADIATOR] failover SqlDB destinations

[Heikki Vatiainen]

On 08/05/2011 10:19 AM, Heikki Vatiainen wrote:

>> Has anyone found any solutions/patches for the sql timeout failover
>> issue with radiator?  When radiator executes an sql statement on an
>> sql server that times out not on connecting, but the statement
>> itself, radiator disconnects and reconnects to the same sql server to
>> try again.  It never seems to failover to the next sql destination.
> 
> Thanks for the problem description and the example code in your other
> message. I will get back to this once I get the comments from the
> development team.

Can you provide a patch for this? That would make sure we have your
version of the fix corretly understood.

There is also the question of possible problems with backwards
compatibility. Currently Radiator does not advance to the next server if
there's a timeout with the query. This change would extend the timeout
behaviour from connections to queries too.

Does anyone see problems with this? Should be made optional? Comments
would be appreciated.

> Can you tell why the problem occurred? Was the DB server having IO
> problems? I'm just curious to know how this happens and how frequent the
> problem might be.

Michael, do you have any comments on this?

>> So, having multiple sql sources seems to be irrelevant with the issue
>> of statement time outs.
> 
> That is currently true.

-- 
Heikki Vatiainen <hvn at open.com.au>

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.