For the second time in two days Facebook bit the big one and disappeared from the face of the planet. The rub today however, is the now ubiquitous like buttons are disappearing on websites everywhere leaving nasty error messages in their wake. Facebook’s Platform status page gives a brief explanation:
Current Status: API Latency Issues
We are currently experiencing latency issues with the API, and we are actively investigating. We will provide an update when either the issue is resolved or we have an ETA for resolution.
Apparently they had the same issue yesterday for a few hours (API latency issues Sep 22, 2010 1:40pm) that forced system wide outages.
Bottom line, it’s the second day of autumn go outside and enjoy the weather. Maybe Facebook will come back some day.
In an entirely unrelated report employers across the country saw a significant increase in employee productivity. Congress will begin an investigation to determine the likely cause of this unexplained increase. 🙂
More Details on Today’s Outage From Facebook
by Robert Johnson on Thursday, September 23, 2010 at 8:29pm
Early today Facebook was down or unreachable for many of you for approximately 2.5 hours. This is the worst outage we’ve had in over four years, and we wanted to first of all apologize for it. We also wanted to provide much more technical detail on what happened and share one big lesson learned.
The key flaw that caused this outage to be so severe was an unfortunate handling of an error condition. An automated system for verifying configuration values ended up causing much more damage than it fixed.
The intent of the automated system is to check for configuration values that are invalid in the cache and replace them with updated values from the persistent store. This works well for a transient problem with the cache, but it doesn’t work when the persistent store is invalid.
Today we made a change to the persistent copy of a configuration value that was interpreted as invalid. This meant that every single client saw the invalid value and attempted to fix it. Because the fix involves making a query to a cluster of databases, that cluster was quickly overwhelmed by hundreds of thousands of queries a second.
To make matters worse, every time a client got an error attempting to query one of the databases it interpreted it as an invalid value, and deleted the corresponding cache key. This meant that even after the original problem had been fixed, the stream of queries continued. As long as the databases failed to service some of the requests, they were causing even more requests to themselves. We had entered a feedback loop that didn’t allow the databases to recover.
The way to stop the feedback cycle was quite painful – we had to stop all traffic to this database cluster, which meant turning off the site. Once the databases had recovered and the root cause had been fixed, we slowly allowed more people back onto the site.
This got the site back up and running today, and for now we’ve turned off the system that attempts to correct configuration values. We’re exploring new designs for this configuration system following design patterns of other systems at Facebook that deal more gracefully with feedback loops and transient spikes.
We apologize again for the site outage, and we want you to know that we take the performance and reliability of Facebook very seriously.