SAN for Genesys logs and/or binaries?

[DJM]

Hi all

Just wanted to get some sort of view of the Genesys community, as we have recently seen some SAN latency issues affecting Genesys apps & causing ADDP timeouts.

It appears that if there are delays (IO blocking) in a Genesys app (such as CSproxy) writing it's log to the SAN, then the app will 'stall' (single threaded?), and not respond to ADDP polls until it regains ability to write it's log buffer..

Does anyone else out there have Genesys Apps logging direct to SAN, or the binaries running on SAN?

Thanks
Dane

[dangermouse]

We write logs to a fibre connected san - never had an issue...

[Gert]

Hi DJM

We had the same issue and only found the cause this week; a slow SAN caused major disruptions in the Call centre. The strange thing is that we did not see this all day every day, things will work fine and the next moment calls will default route, URS will be slow in responding, Link will be slow causing strange errors on the link.

Regards

[DJM]

hi guys, thanks for your responses.

Gert - what was your resolution? - to move off SAN, or *fix* the slow SAN?

Our resolution to our problems were for the storage team to fix the SAN (one of the SAN 'fabrics' was overloaded), but we are considering moving off SAN onto local harddrives. 
 
Seems like a bit of a fundamental issue where inability to write log files means the core application thead 'halts'..

We had Genesys PS come in an do a bit of an audit on our environment, and they generally advised against using SAN for logging.  Seems a bit out of date, given the prevalence of SAN in data centre environments these days

Thanks
Dane