Absolutely perfect!!! Thanks tons... this was what I was going to test, but to see it all diagrammed and details like this is a great validator.
Here's that URL of load balancing / failover AWS config again to be sure it doesn't get garbled in the forum: *http://tinyurl.com/5sghdg * On Tue, Dec 16, 2008 at 11:07 AM, Kevin Baker <[email protected]> wrote: > On Tue, Dec 16, 2008 at 10:57 AM, Alex Kovalyov > <[email protected]>wrote: > >> >> Kevin, >> >> >> On 16.12.08 20:43, "Kevin Baker" <[email protected]> wrote: >> >> > IP take over of the elastic-ip will almost always be faster than >> updating DNS >> > A record with a new IP. >> Is this conclusion based on your tests or something else? > > > Yes, my tests and also research/discussion from other threads. I favor the > idea of putting the responsibility of failover updates on the cluster side > rather than relying on everyone elses servers to update properly. > > Some of it is based on the assumption that not all DNS servers pay > attention to the low TTL on DNS... unfortunate but a reality... also DNS > caching affects this. The IP take-over seems like a more reliable approach > because of TTL and caching issues. The IP take-over response times seem > comparible to the DNS TTL update but again put the update responsiblity on > the cluster rather than trusting that the changes will quickly update across > all the DNS servers on the Internet. > > > > > >> >> >> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
