Forum Discussion
NimbostratusDynamic Ratio Load Balancing. SNMP or WMI
Hey guys,
I have a retail .NET business critical application that is growing beyond simply throwing more nodes into the pool. Certain long running, cpu intensive application jobs are not being distributed evenly among the pool members because of the sporadic nature of the requests. Currently we're using least connections node method and it works fine for everyday client requests, but when something like inventory orders will crush a single server.
My solution to the business of course was dynamic load balancing. I tested the WMI implementation on our RDS Gateway server farm and it works just fine. However, I have little faith in WMI and I am even more concerned about adding an additional IIS application to service the F5 monitor along side the retail app. I implemented the SNMP version and it works fine and solely relies on a simple windows service. I did notice that the weighting seems to be different than WMI. My boss is driving me to us WMI because the documentation suggests it.
So my question is, what is your experience with the WMI implementation of dynamic load balancing? Am I worrying for no reason? Has WMI been reliable, as in no corrupted repositories?
Servers: Win2k8 R2 IIS 7.5 (10-20) Platform: VMWare 5.1
1 Reply
Trevor_L__86504I've put lots of lines into the water about this issue and got some general answers. Support and our sales engineer basically said its up to you and had no specific experience with issues with either SNMP or WMI. I took another look at the configuration document and found that I missed a '\' at the end of the application physical path for scripts in IIS, as well as the pool identity was not set to networkservice. These combination appear to have made the application pool unstable causing it to crash. It appeared as though WMI was failing. After correcting them, it has been running solid. I'll be going with WMI for the monitor. If something changes I'll post it.
