I think most would suggest DNS round robin for more advanced capability I believe some would suggest a custom plug-in
On Nov 18, 2011, at 10:27 AM, sridhar basam wrote: > > > On Fri, Nov 18, 2011 at 9:55 AM, Petzel, David <[email protected]> > wrote: > This feels like it’s about clustering ATS servers, not the origins behind it? > Our design would like something like this: > > LOAD BALANCERS à POOL OF ATS SERVERS à POOL OF ORIGINS. In our case the > origin is the application server. > > > > So we would have say an Active/Passive LB Pair as the externally presented > host. Behind that VIP would be a pool of 3 or more ATS servers (for > redundancy) and each ATS server would use a POOL of origins. From the > examples I’ve seen it appears that there is an assumption by ATS that the > Origin is a VIP, and thus its extracted itself from managing a pool of hosts > for a single origin? > > > > Additionally I saw that there are mapping configurations for using multiple > (different) origins. The ATS Server Pool, seems pretty straightforward, but > specifically I’m trying to find how I would craft a mapping rule such > multiple origins for the same mapping. > > > You could put the origin's behind the LBs too or make the origin an DNS > round-robin record. > > I don't know what ATS would do with these records though, ie if it does > auto-rotation on lookups and if it fails from unresponsive/dead IPs on a > connect. > > Sridhar
