In looking at this issue I've learned three lessons :
- Obviously Google can't (and won't) adjust its upgrade schedules to avoid everyone's deadlines so these problems will continue to occur at inconvenient times. All that you can predict is that in future they will do their upgrades after 9pm USA time (which, of course, is prime working shift for the rest of the world).
- If Google's hardware redundancy is so bad that it can't handle a spike in message traffic when they're doing a PLANNED upgrade, then I don't see how they can hope to handle an UNPLANNED emergency.
- When you're using Google to search the internet for information on Google Applications, don't type the word 'GAPE' into your search bar and hit the 'I'm Feeling Lucky" button (don't do it! trust me on this one!).
The article concludes:
The problem was fixed once Google brought more routers online and spread the traffic among them. Google says it is tweaking its architecture so that the problem doesn't happen again.Sounds like it needs more than a tweak.
.
Posts
1 comment:
Every system, regardless of it's software, is at the mercy of it's networking hardware and the half-starved revolutionaries in third-world countries to whom it is outsourced.
Our own systems today experienced an outage (apparently detecting that I was taking 3 days of annual leave). Again, nothing to do with our software... our outsourced offsite server people dropped the ball (again)... and no, they aren't third world.
Post a Comment