Problems?

Started by psp83, Sep 22, 2010, 19:11:59

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Technical Ben

That facebook error is a gem. Brilliant. Best bug ever. That kind of error is usually considered a virus, for the damage it causes. So it's amazing that they made the mistake of programming it to work that way.
It went like this...

One small error or wrong file: ---> Server checks the master server for a fix: ---> One files was wrong on the master server, so this replies with another error:
This means the Server checks again with the master server for a fix:---> Now the master server is overwhelmed and returns all queries as "error" because it is overloaded:
Now all the Servers think all their files are corrupt, and they all give up, or query the master even more!

It's like a massive feed back loop.  :eek4:
I use to have a signature, then it all changed to chip and pin.

Rik

Until it disappears up its own fundamental orifice...
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

Just think how much bandwidth was saved last night. ;D
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Gary

I mean its not like we get server errors  :whistle:  Facebook have no idea, its only five hundred million users and huge server farms, cant they sort it  ::)
Damned, if you do damned if you don't

Rik

Quote from: Glenn on Sep 24, 2010, 10:33:03
Just think how much bandwidth was saved last night. ;D

:rofl:

I ought to phone and ask.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

netn00b

Quote from: Technical Ben on Sep 24, 2010, 09:46:38
That facebook error is a gem. Brilliant. Best bug ever. That kind of error is usually considered a virus, for the damage it causes. So it's amazing that they made the mistake of programming it to work that way.
It went like this...

One small error or wrong file: ---> Server checks the master server for a fix: ---> One files was wrong on the master server, so this replies with another error:
This means the Server checks again with the master server for a fix:---> Now the master server is overwhelmed and returns all queries as "error" because it is overloaded:
Now all the Servers think all their files are corrupt, and they all give up, or query the master even more!

It's like a massive feed back loop.  :eek4:

awesome job Facebook technies !

i wonder if a few are looking for new jobs today

:thumb:

Rik

They probably haven't been let out yet. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.