We are using apache to load balance many of our web sites. Over the last few weeks, we have migrated sites to new back end servers. With the latest round of migrations (our busiest sites), I am seeing significant performance issues on one of the back end servers. After some investigation, I found that it appears apache is sending the vast majority of requests to the very busy back end server. Further investigation revealed that the configuration for my sites differs from what is in balancer-manager. For example: BalancerMember http://mysite1.myorg.com route=1 BalancerMember http://mysite2.myorg.com route=2 However, if I go to http://myorg.com/balancer-manager, I see: http://mysite1.myorg.com has a route of 2 http://mysite2.myorg.com has a route of 1 So balancer manager is opposite of the config file. In other cases, balancer-manager has the same route defined for each back end server. Something is very odd. Has anyone seen this before? What would be the recommended way to correct it? Thanks, Jeff Jeffrey Poling System Administrator | Information Systems Moody Bible Institute 820 N. LaSalle Blvd., Chicago, IL 60610 312-329-8968 From the Word. To Life. |
|