launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #04313
Re: SSL sessions: start-up latency and renegotiations
On Mon, Aug 16, 2010 at 7:47 PM, Michael Hudson
<michael.hudson@xxxxxxxxxxxxx> wrote:
> On Fri, 13 Aug 2010 11:56:47 +0100, Gavin Panella <gavin.panella@xxxxxxxxxxxxx> wrote:
>> If what I am seeing is valid, then I can see two - I assume relatively
>> easy - things we can do to help:
>>
>> - Only publish one address for each vhost.
>>
I believe two addresses are published so that browsers round-robin DNS
support will failover to the second machine in the case of a webapp FE
server failure. Significantly speeding up SSL would be a worthwhile
reason for moving to another scheme, but you would probably want to do
something to replace the failover mechanism that you are removing. I
think a typical solution is to use a virtual IP with some kind of
heartbeat to let the second frontend takeover if the other one dies.
The downside of something like this is that you are no longer running
active-active on the front ends (I think?).
Speeding up SSL is a very worthwhile effort and it's awesome that this
is being investigated.
--
Elliot Murphy | https://launchpad.net/~statik/
Follow ups
References