4 ms·
Here's the Twilio post-mortem thread on HN: https://news.ycombinator.com/item?id=6093954 https://news.ycombinator.com/item?id=6093954
by mountaineer 13y ago
Here's the Twilio post-mortem thread on HN: https://news.ycombinator.com/item?id=6093954 https://news.ycombinator.com/item?id=6093954
- VladRussian2 13y agodog pile - reminds about FB outage couple years ago when their in-memory cache machines got simultaneously flushed by software update and as result piled up upon MySQL databases for the refresh. Twilio's prohibition of master restart seems like a solution to a consequence only.
- encoderer 13y agoThat's a truly common problem. Experienced the same thing when I was working at Formspring. We relied heavily on Redis and SimpleDB for caching and when a large portion of the cache was lost the site was pretty instantly DOSd. Not fun at all.