Facebook Suffers Actual Cloud In Oregon Datacenter
An anonymous reader writes "The Register carries the funniest, most topical IT story of the year: 'Facebook's first data center ran into problems of a distinctly ironic nature when a literal cloud formed in the IT room and started to rain on servers. Though Facebook has previously hinted at this via references to a 'humidity event' within its first data center in Prineville, Oregon, the social network's infrastructure king Jay Parikh told The Reg on Thursday that, for a few minutes in Summer, 2011, Facebook's data center contained two clouds: one powered the social network, the other poured water on it.'"
And nothing of value was lost.
I dont se any pics in the linked article, Someone has to have pictures of this if it happened...
Welcome to Oregon, it rains a lot.
http://www.mnn.com/lifestyle/arts-culture/stories/artist-creates-beautiful-indoor-clouds
Table-ized A.I.
Superintendant Chalmers: A rain storm? At this time of year? At this time of day? In this part of the country? Localized entirely within your datacentre?
in nasa's vehicle assembly building
The first cloud would be the humidity and condensation sort. The second cloud would be the online service itself. The third cloud, would be the open Internet between the endpoints in a network graph.
What do all these clouds have in common? They're dangerous. The less clouds in your diagram the more you know about your network architecture, latency, and data integrity. The less clouds the better! When a packet goes into the shroud of the cloud in the diagram there's a much higher chance we'll never see it again. This cloud is the one where we must encrypt our data and protect against spoofing and hacking and all forms of data manipulation and latency. The receiving end must be very careful to sanitize the inputs and verify the requests vigorously all because the packet has encountered the cloud. Likewise if we want to interact with an online "cloud" service, we shift the name packet to "our stuff" our login credentials and even bank account info, we have to worry about availability and bandwidth caps when streaming, and unwanted prying eyes from folks we may not desire to have looking, everything becomes far more risky because our stuff touched the cloud service; Far more risky than physically going to the bank or visiting a friend in person would not be subject to. If someone hacks the ATM, the entire bank doesn't lose everyone's credentials. As for the mist filled variety of cloud: It can not only get wet, but if you have a big enough cloud, it can strike you with lightning. We must have surge protections and battery backups against this cloud too.
When I hear people talking about embracing the "cloud" I cringe. "To The Cloud!", in my mind means, "Danger Will Robinson!"
That this happens shows me that they realy optimize their air conditioning for energy consumption.
Traditionally the approach would have been: "Dont think, cool down and re-heat the air constantly to dehumidify it sufficiently". So traditionally you do this dumb with a lot of energy, even if its not needed at all times. What we probably see there is that some control could not (predict or) handle some drop in the inner load (electrial power) in the data center.
The Facebook Oregon datacenter doesn't 'have' air conditioning.
The building is an 'air conditioner'. Its an experimental design...
In the free world the media isn't government run; the government is media run.
Ok, I work for a data center operator. In Central Oregon.
Our data center is so damn dry that most of the time in the summer we're getting alerts about the humidity being too low. How did Facebook fuck this one up?
It's clouds all the way ... up?
Both clouds were leaking and pissing off users. Facebook must have real sysadmins.
Not just the people, but yes, static electricity is the primary concern. Also, I'm told by the people that manage these sorts of things that a "too dry" environment also makes air cooling less effective. Something to do with the fact that a little bit of moisture actually allows the air to carry more heat than if it was 100% dry.
No, you are (mostly) wrong.
What happened was that the system malfunctioned which led to hot and humid air being circulated throughout the system. This normally would not cause condensation. However, all of the equipment was previously cold (because the system was working normally before it failed). The hot and humid air came into contact with cold components (various components in the power supply and computer casing). This caused condensation (because the hot and humid air contacted the cold components, cooled down, and had to ditch some of its water due to thermodynamics). The condensation on components of the power supply was then blown into various PCB components when the maintenance staff increased the airflow in the datacenter in an attempt to bring the temperature down. The condensation hitting the PCB caused what you would expect when dumping water onto electronics: stuff shorted out and failed.
You're correct insofar as that humidity was not properly controlled, but this was hardly a case of idiots at the controls or at the drawing board. This was an unanticipated failure mode that was experienced because of a faulty control sequence being generated.
-1 disagree is not a modifier for a reason. -1 troll, flaimbait, redundant, overrated are NOT acceptable substitutes.