(RADIATOR) High availability radius

[Igor Briski]

Hello!

We had some problems in the past regarding our main database server
(Oracle). The problem is, when the database slows down (it is still
accepting connections but runs very slow) Radiator starts slowing down
too and my NAS boxes eventually timeout. So all my users start getting
rejected. 

Both of our Radiator servers connect to the same database, so we
generally have a single point of failure. 

Is there any way to configure Radiator so that when it detects a very
slow database it stops using it (similar behaviour when the database
goes down, it backs off). 

Authorization part is using .db files, so when the database is not
available authorization can continue. But when the database is slow, the
whole thins slows down to a point where the system is not usable. 

Any comments, suggestions? 

-- 
Igor Briski <igor.briski at iskon.hr>

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.