Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google outage – resolved

news.ycombinator.com

Post reply on HN
Print view View original

801–810 of 870 posts

Re: Google outage – resolved

#801

Post by savanaly »

yjftsjthsd-h wrote: post #767
ithkuil wrote: post #661

Earlier quoted context omitted.

Isn't this a good indication that the performance problem if gmail may not be related to the "bloat" of the frontend itself?

It might suggest that the frontend isn't the only issue, at least - and maybe this explains why it's usually so slow, if the frontend can be fast on a fast enough backend. On the other hand, the speed of the "basic HTML" version implies that the frontend can be the issue.

Entirely possible as well that the "basic HTML" uses different API service in the background that are snappier for comparative lack of users.

Re: Google outage – resolved

#802

Post by s3cur3 »

nickjj wrote: post #719
kaushikt wrote: post #676

Earlier quoted context omitted.

why?

This topic just came up recently on a podcast I was on where someone said a large service was down for X amount of time and the service being down tanked his entire business while it was down for days. But he was compensated in hosting credits for the exact amount of down time for the 1 service that caused the issue. It took so long to resolve because it took support a while to figure out it was their service, not hi…

> . . . like going to a restaurant, getting massive food poisoning, almost dying, ending up with a $150,000 hospital bill and then the restaurant emails you with "Dear valued customer, we're sorry for the inconvenience and have decided to award you a $50 gift card for any of our restaurants, thanks!".

It's even slightly worse than that. SLAs generally refund you for the prorated portion of your monthly fee the service was out, so it's more like "here's a gift card for the exact value of the single dish we've determined caused your food poisoning." Hehe.

Re: Google outage – resolved

#803

Post by rachelbythebay »

eric_khun wrote: post #669

If you pay for Google Services, they have an SLA (service level agreement) of 99.9% [1]. If their services are down more than 43 minutes this month[2], you can request “free days” of usage. Edit: Services were down from ~12:55pm to ~1:52pm, it's 57minutes. Thanks hiby007 [1] https://workspace.google.com/intl/en/terms/sla.html [2] https://en.wikipedia.org/wiki/High_availability#Percentage_c...

Your nines or their nines?

I bet if you personally can't use it, but their overall reliability meets the bar, then they're within SLA.

Don't ask why I know this.

Re: Google outage – resolved

#804

Post by nickjj »

s3cur3 wrote: post #802
nickjj wrote: post #719

Earlier quoted context omitted.

This topic just came up recently on a podcast I was on where someone said a large service was down for X amount of time and the service being down tanked his entire business while it was down for days. But he was compensated in hosting credits for the exact amount of down time for the 1 service that caused the issue. It took so long to resolve because it took support a while to figure out it was their service, not hi…

> . . . like going to a restaurant, getting massive food poisoning, almost dying, ending up with a $150,000 hospital bill and then the restaurant emails you with "Dear valued customer, we're sorry for the inconvenience and have decided to award you a $50 gift card for any of our restaurants, thanks!". It's even slightly worse than that. SLAs generally refund you for the prorated portion of your monthly fee the servic…

You're right and the funny thing is that's exactly what he said after I chimed in.

Re: Google outage – resolved

#805

Post by gberger »

ttn wrote: post #435
mozinator wrote: post #322

edit: added details edit: redacted my phone number edit: big mistake to add phone number edit: I think illic is right, probably not me edit: removed details

If you are right; congrats! you just got few googlers fired!

Google doesn't fire people who cause outages.

Re: Google outage – resolved

#806

Post by awesomemonster »

FloatingUp wrote: post #725
b0afc375b5 wrote: post #711

Earlier quoted context omitted.

I'm so glad I'm not the only one feeling deployment anxiety. The project I'm involved in doesn't really have serious money involved, but when there's a regression found only after production deployment my stress levels go up a notch.

When I was working at a pretty big IT provider in the electronic banking sector, we (management and senior devs) made it an unspoken rule, that: - Juniors shall also handle production deployments regularly. - A senior person is always on call (even if only unofficially / off the clock). - Junior devs are never blamed for fuckups, irrespective of the damage they caused. That was the only way to help people develop rou…

Same thing -- used to work at a very large hosting provider. One of our big internal infra management teams wouldn't consider newhires fully "part of the team" until they had caused a significant outage. It was genuinely a right of passage, as one person put it, "to cause a measurable part of the internet to disappear".

I got to see a lot of people pass through this right of passage, and it was always fun to watch. Everyone would take it incredibly seriously, some VP would invariably yell at them, but at the end of the day their managers and all their peers were smiling and clapping them on the back.

Re: Google outage – resolved

#807

Post by mav3rick »

xtracto wrote: post #790

On reddit thread there are some really good jokes about this [1] related to their asinine interview questions. Like: > Did they try to fix them by inverting a binary tree? >> Yeah maybe implementing a quick LRU cache on the nearest whiteboard will help them out here >> Did they try checking what shape their manhole cover is? >> Dev ops was too busy out counting all the street lights in the United States [1] https://w…

None of these are asked in G interviews. The commenters are asinine.

Re: Google outage – resolved

#808

Post by xtracto »

mav3rick wrote: post #807
xtracto wrote: post #790

On reddit thread there are some really good jokes about this [1] related to their asinine interview questions. Like: > Did they try to fix them by inverting a binary tree? >> Yeah maybe implementing a quick LRU cache on the nearest whiteboard will help them out here >> Did they try checking what shape their manhole cover is? >> Dev ops was too busy out counting all the street lights in the United States [1] https://w…

None of these are asked in G interviews. The commenters are asinine.

No?

https://twitter.com/mxcl/status/608682016205344768?lang=en

Re: Google outage – resolved

#809

Post by cuspycode »

forgotmypw17 wrote: post #538
jacquesm wrote: post #196

So, anybody still feel like arguing that 'the cloud' is a viable back-up? Or is that a sore point right now? Just for a moment imagine: what if it never comes back again? Of course it will, - at least, it better - but what if it doesn't? And if it does, are you going to take countermeasures in case it happens again or is it just going to be 'back to normal' again?

Most of the things I backed up for myself are either gone forever or irretrievably lost. Most of the things I backed up with google remain largely accessible, except for an occasion like this. It's rare that any services I operate solo come back this quickly after there is a downing issue.

I have the opposite experience, at least with regard to your first two paragraphs. Most of the things that I have backed up on other people's computers over the past 3-4 decades are irretrievably lost. But most of the things that I have taken care to make backups of on personal equipment over the years, are still with me.

Cloud storage is still useful of course, but I prefer to view it as a cache rather than as a dependable backup.

Re: Google outage – resolved

#810

Post by abstractbarista »

mav3rick wrote: post #807
xtracto wrote: post #790

On reddit thread there are some really good jokes about this [1] related to their asinine interview questions. Like: > Did they try to fix them by inverting a binary tree? >> Yeah maybe implementing a quick LRU cache on the nearest whiteboard will help them out here >> Did they try checking what shape their manhole cover is? >> Dev ops was too busy out counting all the street lights in the United States [1] https://w…

None of these are asked in G interviews. The commenters are asinine.

Not necessarily true. Some of these most certainly have been.
Post reply on HN