3 ms·
That was my initial thought as well. But, low disk space on the master DB? And you need a human to go futz around with it? There is either a whole lot of missin
by jfoutz 9y ago
That was my initial thought as well. But, low disk space on the master DB? And you need a human to go futz around with it? There is either a whole lot of missing monitoring and automation, or those are completely worthless pages.
I understand the freakout, i assume it could take down the site. But, like, not responding to a page is like the very last on the list of things to fix. Calling in random engineer is pretty much last ditch, hail mary, the world is on fire, oh fuck we're going to go out of business disaster. At a certain point, you kind of have to assume one possibility is your oncall person is dead. Whatcha gonna do then?
I seriously doubt all of their careful high availability planning failed. I would bet their paging is (hopefully was) just stupid.
- oh_sigh 9y agoFrom the article, it's not that the engineer never responded. The engineer acknowledged the pages but never did anything to correct the problem beyond that. I agree with you though that a random engineer might not have the tools and knowledge ready to fix something like that, but that is why you can let the pages escalate until you wake someone up who does.