Today IIS team has published a servicing release of Web Farm Framework 2. This release contains fixes for the bugs reported in version 2.0 that was published in January this year. The following bugs have been fixed in this release:
- If a server was excluded from load balancing because of an error or if it was temporary unavailable then it required administrator to manually add it back. With this release the Web Farm Service will attempt to auto-repair unavailable servers and add them back to load balancing once they become healthy again.
- Non-standard HTTP ports could not be used when communicating with servers in web farm.
- Error caused by race condition between when applicationHost.config is updated and when service reads the configuration.
- Service attempted to add firewall exception and failed if firewall service was not running.
- MSDeploy 1.1 was always installed on servers in the farm, even if MSDeploy 2.0 was available.
- Recycling of the app pool on the controller resulted in HTTP 502 errors.
- Secondary servers kept synchronizing the same changes over and over again.
- When primary server came back after downtime, the provisioning did not start automatically.
- Sync Error “An item with the same key has already been added.”
- User profile was not loaded when service was installed which caused installation failures.
Install the Web Farm Framework 2.1
To install Web Farm Framework 2.1 use the download links at the project’s home page at http://www.iis.net/expand/WebFarmFramework.
If you have Web Farm Framework 2.0 already installed, then it will be updated to v2.1. Note that a reboot maybe required during update and after the reboot the WebFarmService must be restarted on the controller server by using the command below:
net start webfarmservice
More information
ruslany on July 29th 2011 in Other
2,278 views
Today IIS team has released to web the Web Farm Framework 2.0. This is the final, production ready version that has several new features and improvements listed below:
- Workflow Builder is used to define and schedule custom tasks that can be run on all servers in the farm. The tasks can be scheduled to run periodically or can be started manually by an administrator. An example of such task could be a msdeploy command to partially sync web site content.
- Windows Credential Store support allows to store the administrator credentials used for server provisioning in a secure Windows Credential Store. This enables an added layer of security when dealing with credentials in Web Farm Framework.
- Third party load balancers support via Web Farm Framework extensibility. It is possible to configure Web Farm Framework to integrate with hardware load balancers instead of relying on IIS Application Request Routing module.
- Improved support for advanced MSDeploy operations. Options of MSDeploy can be used with Web Farm Framework for advanced deployment scenarios.
- Improved support for syncing large amount of files. Several issues related to syncing large amount of files across web farm nodes have been fixed.
In addition to that many bugs reported by beta users were fixed in this release.
Install the Web Farm Framework 2.0 – RTW
To install Web Farm Framework 2.0 use the download links at the project’s home page at http://www.iis.net/expand/WebFarmFramework.
If you have a beta build of Web Farm Framework 2.0 already installed, then it needs to be uninstalled prior to installing RTW build.
More information
ruslany on January 20th 2011 in Other
3,814 views
IIS team has recently released a Web Farm Framework 2.0 beta. The goal of the Web Farm Framework is to enable easy provisioning, deployment and managing of web farms. This blog post provides an example of what Web Farm Framework can do and how it can simplify the Web Farm management tasks.
To demonstrate the capabilities of the tool, we will create a simple web farm that looks as on the following diagram:
- The load balancer will be using the Application Request Routing for IIS 7 and will also act as a Web Farm Controller. Web Farm Controller manages all the machines within the web farm and it has the Web Farm Framework 2.0 installed.
- The Primary Server, in addition to serving the web requests, also acts as an example server for all the other servers in the farm. Web Farm Framework will ensure that every new secondary server added to the web farm has exact same components installed and is configured exactly as the primary server.
- The Secondary Server(s) will serve web requests. It’s configuration and content matches the primary server. Continue Reading »
ruslany on July 30th 2010 in Other
11,476 views
