I would wonder - as others suggested - that they may have stretched the cluster across datacenters ?!
Would be interested in the post-mortem.
41–50 of 88 posts
I would wonder - as others suggested - that they may have stretched the cluster across datacenters ?!
Would be interested in the post-mortem.
DO is a nice thing to play around with and maybe launch something, but I wouldn’t run full production on it.
Thank you Digital Ocean for once again proving that 'The Cloud' is not a backup.
This is OT, but I have a droplet on DO and I'm amazed at the amount of malicious traffic it gets. Is it normal for a very private vps to receive thousands of ssh attempts per hour? I have fail2ban installed and the jail is so busy it's quite astounding. Anyone with more web hosting experience that can weigh in?
What unholy thing did they do that broke it across 12 different datacenters, good lord.
This is OT, but I have a droplet on DO and I'm amazed at the amount of malicious traffic it gets. Is it normal for a very private vps to receive thousands of ssh attempts per hour? I have fail2ban installed and the jail is so busy it's quite astounding. Anyone with more web hosting experience that can weigh in?
Fail2ban is great to at least stem the tide. It's good at slowing down SSH brute forcing, and can be set up to throttle poorly behaved scrapers so your site isn't getting hammered constantly. If you can deal with the inconvenience, it's even better to put services that don't need to be truly public behind an IP whitelist. That stops the vast majority of malicious traffic, most of which is going after the low hanging fruit anyway.
Otherwise, it's kinda just a fact of life. With the good traffic also comes the bad.
What unholy thing did they do that broke it across 12 different datacenters, good lord.
Earlier quoted context omitted.
This does seem to indicate a notable lack of isolation for the blast radius between DO datacenters. Would be interesting to see the post mortem.
Google Cloud recently had a global outdate. DevOps tools that interact with all resources across data centers are primarily the culprit.
Reading between the lines, it looks like their maintenance system needed to take down several Borg clusters within a single AZ, and their BGP route reflectors all ran from the same set of logical clusters. They'd tried to set up geo-redundancy by having different BGP speakers across different AZs, but they were all parented by the same set of logical clusters, and the maintenance engine descheduled all of them together. Then the network ran okay ("designed to fail static for short periods of time") until the routes expired, after which routes got withdrawn and traffic blackholed.
They realized the issue within an hour.. unfortunately, since they took down multiple replicas of their network control plane, they lost Paxos primary and had to rebuild configuration.
(Disclaimer: I work in Azure, I just find it fascinating to look at Google's RCAs because failure provides an insight into their architecture and risk engineering.)
This is your weekly reminder that anything you want to be reasonably “HA” should span multiple vendors in multiple DCs.