[138903] in North American Network Operators' Group
Re: OT: Question/Netflix issues?
daemon@ATHENA.MIT.EDU (George Herbert)
Tue Mar 22 21:27:50 2011
In-Reply-To: <55b67f74-ea3d-4843-8c01-4278d2ee011d@e21g2000yqe.googlegroups.com>
Date: Tue, 22 Mar 2011 18:27:05 -0700
From: George Herbert <george.herbert@gmail.com>
To: Ryan Malayter <malayter@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Tue, Mar 22, 2011 at 6:20 PM, Ryan Malayter <malayter@gmail.com> wrote:
>
>
> On Mar 22, 7:47=A0pm, Jeff Kell <jeff-k...@utc.edu> wrote:
>> Now getting "We re sorry, the Netflix website and the ability to
>> instantly watch movies are both temporarily unavailable." out of Charter=
.
>>
>> Campus getting same routed via 1239 209 2906.
>>
>> Jeff
>
> Guess that move to Amazon EC2 wasn't such a good idea. First reddit,
> now netflix.
> http://techblog.netflix.com/2010/12/four-reasons-we-choose-amazons-cloud-=
as.html
>
> I suppose there's a reason you can't get an SLA with any teeth from
> Amazon...
You're assuming that the outage was somehow related to the quality of
hosting (virtual server, instance management, etc).
In my experience with large website failures, some of mine and talking
to others at conferences and elsewhere, I can't recall one where the
servers HW performance / virtualization management were the root cause
(and only one that was intrinsically hardware-based, which was a
catastrophic storage failure and not server failure). Configuration
management, inadequate testing of new software, systems management
error, DBMS throughput capacity, emergent software / architecture
failures are the usual culprits.
--=20
-george william herbert
george.herbert@gmail.com
