3 ms·
> Google engineers were alerted to the issue within 3 minutes and began immediately investigating As a user of their service, our engineers were notified withi
by nashadelic 8y ago
> Google engineers were alerted to the issue within 3 minutes and began immediately investigating
As a user of their service, our engineers were notified within <30 secs when the issue started. Given GCP had a large population impacted, how is it that it took them much longer to acknowledge?
> The GFE development team was in the process of adding features to GFE to improve security and performance. These features had been introduced into the second layer GFE code base but not yet put into service. One of the features contained a bug which would cause the GFE to restart; this bug had not been detected in either of testing and initial rollout.
Something going down after a deployment is the most common source of issues. A system KPI abnormality after a rollout should be common practice to monitor and to perform an almost instant auto-rollout on. Also, doesn't GCP perform dark launched, partial launches? Launch to 1%, see KPIs, increase to 5% and so on?
- foobaw 8y agoMaybe they were on reddit. Seriously though, 30 seconds vs 3 minutes is a long time in the reliability world but not atrocious.
- smueller1234 8y agoIt's the difference between being at home, sober, and with a laptop handy vs. being actively logged in and ready to go at all times. In terms of quality of life for people on call, it's an entirely different world. And in a setup where your oncall engineers are extremely highly skilled and have all the choice in the world in terms of where to work, that little bit of respect of their time is a necessary investment.