Finally, I have the BroadcastPollingProvider implementation of the webfarm set up and functioning correctly. For some reason, one of my webservers kept making entries (around 20 per second) into the Servers table. Most of the entries in the LastPollDate where Null and occasionally one had a date. I was up to 1,000,000 + and growing when there should only be one entry per server. (Database size was 100Gig and increasing) I checked the provider code and could see why the entries where doing this yet, I don't know what started the issue. It lost its head somewhere when we were setting it up initially I guess. So, what I did to remedy the situation was to purge all entries for the problematic server in the Servers and Broadcasts table. So far after 24 hours I only have an entry per server in the servers table with an updating lastpolldate. I have no entries so far in the cached objects table. The broadcasts table has been growing but I don't think it has grown to the point where the cleanup script starts purging. I will keep an eye on that though.
Also for those that are trying to implement the alternative webfarm environment, notice that in the web farm support document dated June 20, 2006 on page 10 the second bullet point reads:
Schedule Enabled" so it is checked. Click "Update".
I initially thought that maybe I should enable the DotNetNuke.Services.Cache.PurgeCache, DOTNETNUKE scheduled task since the first line in the "Supported Configuration" section on page 9 had some similar language:
A scheduled task needs to be enabled. Log in as a SuperUser, go to the Host menu
and select “Schedule”. Edit the scheduled task
“DotNetNuke.Services.Cache.PurgeCache, DOTNETNUKE” by clicking on the edit
icon next to the scheduled task. Select the checkbox labeled “Schedule Enabled” so
it is checked. Click “Update”.
The DotNetNuke.Services.Cache.PurgeCache, DOTNETNUKE scheduled object does not need to be enabled. If it is enabled, then when you view its history it gives a message saying it is not necessary with the BroadcastPollingProvider.
I hope this brain dump may help someone who finds themselves in similar shoes. I could have used a post like this about a week ago!