[38538] in North American Network Operators' Group
RE: Hosting Failover Question
daemon@ATHENA.MIT.EDU (Paul Froutan)
Wed Jun 6 19:48:28 2001
Message-Id: <5.1.0.14.2.20010606171541.07ee52f0@pop3.rackspace.com>
Date: Wed, 06 Jun 2001 18:46:33 -0500
To: nanog@merit.edu
From: Paul Froutan <pfroutan@rackspace.com>
In-Reply-To: <23D5B89EC7B4D311821400805F85082C02EAABB7@tac-nt6.ab.tac.ne
t>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Errors-To: owner-nanog-outgoing@merit.edu
Ideally, I wouldn't find any kind of "session" to time out. Almost
everyone is fine with short outages (few seconds) as long as their apps
don't time out. While 5 seconds is great, I think you'll have a hard time
getting there. You'll have to exchange tons of "hello" type packets which
means you're flooding a lot of traffic. You can control it at ports, but
it's still a pain.
At 6/6/01, you wrote:
>I am interested what I should design to.
>
>-----Original Message-----
>From: Paul Froutan [mailto:pfroutan@rackspace.com]
>Sent: Wednesday, June 06, 2001 1:23 PM
>To: Nanog@Merit. Edu (E-mail)
>Subject: Re: Hosting Failover Question
>
>
>
>What do you mean by "reasonable"? Do you mean what you can expect right
>now at a hoster, or what you should aim for when designing a system?
>
>At 6/6/01, James DeMong wrote:
>
>
> >I am looking for a Rule of Thumb on failover for hosting, mostly
> >tcp(webserver), some udp (audio/video streaming) stuff.
> >My thought is that 5 seconds to failover when a network
> >element(switch/router/load balancer/FW) fails is reasonable.
> >
> >How many seconds is reasonable for fail over in such a situation?
> >
> >Thanks in advance.
> >__
> >James DeMong
> >Network Design Specialist
> >TELUS Advanced Communications
> >Phone: (403) 503-3718
> >Email: James.DeMong@telus.com
>
>----------------------------------------------------------------------
>Paul Froutan Email: pfroutan@rackspace.com
>Rackspace Managed Hosting <http://www.rackspace.com>
