[154272] in North American Network Operators' Group
Re: FYI Netflix is down
daemon@ATHENA.MIT.EDU (Todd Underwood)
Sat Jun 30 15:05:03 2012
In-Reply-To: <4FEF4394.2030108@rollernet.us>
Date: Sat, 30 Jun 2012 15:04:22 -0400
From: Todd Underwood <toddunder@gmail.com>
To: Seth Mattinen <sethm@rollernet.us>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
This was not a cascading failure. It was a simple power outage
Cascading failures involve interdependencies among components.
T
On Jun 30, 2012 2:21 PM, "Seth Mattinen" <sethm@rollernet.us> wrote:
> On 6/30/12 9:25 AM, Todd Underwood wrote:
> >
> > On Jun 30, 2012 11:23 AM, "Seth Mattinen" <sethm@rollernet.us
> > <mailto:sethm@rollernet.us>> wrote:
> >>
> >>
> >> But haven't they all been cascading failures?
> >
> > No. They have not. That's not what that term means.
> >
> > 'Cascading failure' has a fairly specific meaning that doesn't imply
> > resilience in the face of decomposition into smaller parts. Cascading
> > failures can occur even when a system is decomposed into small parts,
> > each of which is apparently well run.
> >
>
>
> I honestly have no idea how to parse that since it doesn't jive with my
> practical view of a cascading failure.
>
> ~Seth
>
>
