Tuesday, 17 May 2011

Adventures Into Web Farm Framework 2.0

I have been using the Web Farm Framework 2.0 to handle the load balancing and provision of the applications. Our web farm consists of four servers, 1 load balancer, 2 web servers and 1 database server. The installation was simple enough using the Web Platform Installer.

The web platform installer was used to install the Web Farm Framework 2.0 onto the load balancer. The guide "Setting up a Server Farm with the Web Farm Framework 2.0 for IIS 7" provides an easy walk through for getting your web farm setup. However once it has been setup there are a number of steps that still had to be configured to ensure the web farm worked correctly.

Before completing the following steps I ran into a an issue where the server would appear available for load balancing in the "Servers" view, but would be unavailable in the "Monitoring and Management" view. To resolve try the following steps.

1. Health Test Url

Make sure that the health test url has been set. The application request routing uses this to test whether a server should be used for load balancing.

2. Default App Pool Settings

Edit the advanced settings of the DefaultAppPool on the controlling server and set the recyling value for "Regular Time Interval (minutes)" to zero.

3. Set Primary and Secondary Servers to Response to Ping

Update the firewall settings on the Primary and Secondary servers to respond to ping.

These are thing steps that I followed to get it to work correctly, they might vary for you depending on your setup.

1 comment:

  1. Kris Van de Vijver10 January 2012 at 03:24

    Hi John, we have the same problem. Did these steps solve the issue permanently for you?