That would be great if that was how it always worked. It is true that some, most, modern browsers will attempt to try the second/n address after attempting to connect for a few seconds. Unfortunately there are other issues like DNS caching, proxies, mobile browser etc that either don't support or disrupt the IP failover. In these cases it will resolve to the first IP, if that fails then it will just error out.
The round-robin does help with failover, but is more to distribute load to clustered applications. This is part of the reason for floating IP's. If a server fails then a different server can take over the IP and inherit the load that would be sent to the server from the round robin. That being said, I was hoping that people who use scalr had best practices or possibly Scalr has some IP take over "magic" for servers that go down. I know that an Elastic IP can be set to a server role and then reassigned to a new instance that is replacing a failed one. This might be good enough if it comes up fast enough... just looking for some tips. Thanks, - Kevin On Mon, Dec 15, 2008 at 11:46 PM, Frédéric Sidler <[email protected] > wrote: > > That is why round robin exists. The browser will detect that one ip is > not responding and will send the request to the second one. > > 2008/12/16, Kevin Baker <[email protected]>: > > We have tested our app servers for failover. Works great! > > > > I wasn't sure of best practices for the "www" front-end role though. I > was > > planning on having two "www" instances setup in round-robin with two > elastic > > IP's. However, if one of these servers went down, one of the elastic IP's > > would be pointing at a "dead" ip until the new "www" instance came up. > What > > would be the best way to handle this so that we do not have a > > single-point-of-failure with our "www" role? > > > > I was thinking if the elastic-ip for the failed instance was reassigned > to > > the active "www" instance while the new instance was coming up it would > > reduce the down time... > > > > Thoughts? > > > > > > Thanks, > > > > - Kevin > > > > > > > > > -- > Envoyé avec mon mobile > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
