(imported comment written by SystemAdmin)
spdracers,
Here is a way to do relay auto selection. We use this effectively with over 1100 relays. First we set up a pool of central relays on the same LAN as the root server. The number of these will need to be computed based on load, type and size of relay. The performance of the disk subsystem is your most important consideration. Go for more/faster drives over a faster cpu.
In our pool of central relays, we designate one as the failover in the Adverstisement list. The rest of the relays get assigned a unique Advertisement name across all of them.
Side note: Is it important to work with your network engineers so that each central relay is the same hop count from your remote sites.
Now on the remote relays, set the following in a custom action:
setting “_BESClient_RelaySelect_FailoverRelay”=“http://:52311/bfmirror/downloads/” on “{now}” for client
setting “__RelaySelect_Automatic”=“1” on “{now}” for client
setting “_BESClient_Relay_EnableAutomaticSelection”=“1” on “{now}” for client
setting “_BESRelay_Register_Affiliation_AdvertisementList”="<unique local advertisement name based on location/function>"on “{now}” for client
setting “_BESClient_Register_Affiliation_SeekList”=";" on “{now}” for client
On clients in the remote location set the following:
setting “_BESClient_RelaySelect_FailoverRelay”=“http://:52311/bfmirror/downloads/” on “{now}” for client
setting “__RelaySelect_Automatic”=“1” on “{now}” for client
setting “_BESClient_Register_Affiliation_SeekList”=";;" on “{now}” for client
In this manner, remote relays will prefer the primary central array of relays, but they also have a failover. Remote clients use their local relay as their preferred primary, but can fail over to a central primary, then finally the central failover relay as needed.
Optionally, you may wish to throttle communications between remote and central relays. One way to accomplish this is limiting simultaneous connections on the central relays:
setting “_BESRelay_HTTPServer_MaxConnections”="" on “{parameter “action issue date” of action}” for client