[154279] in North American Network Operators' Group
Re: FYI Netflix is down
daemon@ATHENA.MIT.EDU (Scott Howard)
Sat Jun 30 16:20:27 2012
In-Reply-To: <CAB2RJygZbz76R6XveivnUT9vyuadO=S=+ULRA0=Z0TYWiaY6Wg@mail.gmail.com>
Date: Sat, 30 Jun 2012 13:19:54 -0700
From: Scott Howard <scott@doc.net.au>
To: Todd Underwood <toddunder@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Sat, Jun 30, 2012 at 12:04 PM, Todd Underwood <toddunder@gmail.com>wrote:
> This was not a cascading failure. It was a simple power outage
>
> Cascading failures involve interdependencies among components.
>
Not always. Cascading failures can also occur when there is zero
dependency between components. The simplest form of this is where one
environment fails over to another, but the target environment is not
capable of handling the additional load and then "fails" itself as a result
(in some form or other, but frequently different to the mode of the
original failure).
Whilst the Amazon outage might have been a "simple" power outage, it's
likely that at least some of the website outages caused were a combination
of not just the direct Amazon outage, but also the flow-on effect of their
redundancy attempting (but failing) to kick in - potentially making the
problem worse than just the Amazon outage caused.
Scott
