Feeds

Worldwide Gmail crash was due to Google Sync bug

Engineer: How Oompah-Loompah config foul-up pulled down world's email

Secure remote control for conventional and virtual desktops

It was a Googler misconfiguring a sync server that took out Chrome and Gmail on Monday, an engineer has stated on dev forums.

The reason for Gmail's brief burnout on Monday has been winkled out, and it was connected to the rolling crashes suffered on the Chrome browser on the same day.

It was a human error in configuring a Chrome component that throttled traffic in Chrome and then on several other Google services, explained Chrome engineer Tim Steele in a post on the Google code forum.

The component controlled traffic for Chrome Sync - a service that allows users to synchronise their customised Chrome browser across all of their devices, giving them the same bookmarks, widgets, settings and browsing history.

A small change to its configuration settings meant the load-balancing component started to throttle traffic when it wasn't supposed to. And because the component is core to the infrastructure that many Google services depend on, it affected them too.

It was Chrome Sync users who were hit by the outage first.

Steele explained:

- Chrome Sync Server relies on a backend infrastructure component to enforce quotas on per-datatype sync traffic.
- That quota service experienced traffic problems today due to a faulty load balancing configuration change.
- That change was to a core piece of infrastructure that many services at Google depend on. This means other services may have been affected at the same time, leading to the confounding original title [the Gmail bug] of this bug.
- Because of the quota service failure, Chrome Sync servers reacted too conservatively by telling clients to throttle "all" data types, without accounting for the fact that not all client versions support all data types.

The crash is due to faulty logic responsible for handling "throttled" data types on the client when the data types are unrecognized.

There is WRONG in the cloud. ®

Internet Security Threat Report 2014

More from The Register

next story
Azure TITSUP caused by INFINITE LOOP
Fat fingered geo-block kept Aussies in the dark
NASA launches new climate model at SC14
75 days of supercomputing later ...
Yahoo! blames! MONSTER! email! OUTAGE! on! CUT! CABLE! bungle!
Weekend woe for BT as telco struggles to restore service
You think the CLOUD's insecure? It's BETTER than UK.GOV's DATA CENTRES
We don't even know where some of them ARE – Maude
Cloud unicorns are extinct so DiData cloud mess was YOUR fault
Applications need to be built to handle TITSUP incidents
BOFH: WHERE did this 'fax-enabled' printer UPGRADE come from?
Don't worry about that cable, it's part of the config
Stop the IoT revolution! We need to figure out packet sizes first
Researchers test 802.15.4 and find we know nuh-think! about large scale sensor network ops
DEATH by COMMENTS: WordPress XSS vuln is BIGGEST for YEARS
Trio of XSS turns attackers into admins
prev story

Whitepapers

Why cloud backup?
Combining the latest advancements in disk-based backup with secure, integrated, cloud technologies offer organizations fast and assured recovery of their critical enterprise data.
Getting started with customer-focused identity management
Learn why identity is a fundamental requirement to digital growth, and how without it there is no way to identify and engage customers in a meaningful way.
Driving business with continuous operational intelligence
Introducing an innovative approach offered by ExtraHop for producing continuous operational intelligence.
5 critical considerations for enterprise cloud backup
Key considerations when evaluating cloud backup solutions to ensure adequate protection security and availability of enterprise data.
High Performance for All
While HPC is not new, it has traditionally been seen as a specialist area – is it now geared up to meet more mainstream requirements?