The NE US and Brazil hit hardest?
Posted on 11/12/2018 10:16:18 AM PST by Revel
Did not log in (I have no account there), but it appears to be up.
When I deleted my FB account a month ago, I told suckerberg this would happen.
No, my Bro In Law son came out Sunday on Facebook. That is what likely blew it up.
The NE US and Brazil hit hardest?
And nothing of value was lost on that day.
I despise FaceBook — but alas it is all up and fine for me.
Trump has his buddy Vlad handle it, so there would be plausible deniability.... LOL
.
Hopefully all databases have been purged, world wide!
Remember, CIA director is one of us now.
.
Get out the white chalk.
fakebook response(I am not a member, but it is still down for me)
https://www.facebook.com/notes/faceb.../431441338919/
More Details on Today’s Outage
By Robert Johnson on Thursday, September 23, 2010 at 5:29 PM
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.
This is heart breaking. - - NOT!
A brief respite of sanity.
Installing ChiCom political censorship firewall software is taking longer than they thought.
We ALL will be healthier, happier and wealthier as long as FaceSlut is down!
No loss!
Not a member either but reports are that it’s up and working.
Who CARES?
So the people at Facebook can’t get it up. Not surprising.
Deleting files that will be used in draining the swamp, capturing the swamplings, and putting them in little jars.
Who has those files? hmmmm.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.