On Dec 16, 2008, at 7:47 AM, harrisb <[email protected]> wrote:
>
> Doesn't AWS restrict the use of elastic IPs so that only one can point
> to any instance at a time?
>
Yup. But it can be switched to another machine if one goes down. As
Alex pointed out though, there is a delay.
> On Dec 15, 5:36 pm, "Kevin Baker" <[email protected]> wrote:
>> 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
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
