Re:Amazon EC2 outage: summary and lessons learned
by pumpmylemma on Monday April 25, 2011 @04:43PM
(#2482808)
I don't think it was a symptom of routing synchronization specifically, but I'd be curious to know if it was a case of unexpected and undesired synchronization. (E.G. An independent and random cluster of blocks suddenly updated; the network was saturated; it pulled in more updates; ...)
And yes, the paper talked about randomization. It also pointed out the magnitude of randomization required was larger than expected.
Re:Amazon EC2 outage: summary and lessons learned
by pandakar on Monday April 25, 2011 @06:12PM
(#2483140)
Has there been an official explanation?
Re:Amazon EC2 outage: summary and lessons learned
by pumpmylemma on Monday April 25, 2011 @06:39PM
(#2483220)
As far as I'm aware, no. That's why RightAWS said they get an F for communication.
The solution (I didn't reread so this is from memory) is to add random jitter to each participant's timer.
However, is there evidence to suggest that's what happened to Amazon? I can see this being a big issue in '93 with high-latency low-bandwidth links a commonplace. But we think that Amazon wasn't engineered well enough to deal with multiple orders of magnitude spikes in C&C traffic?
Thank you, though, for posting a (much needed) technical comment to this discussion.