Re:MongoDB's lead developer: Foursquare outage post mortem
by voxxit on Thursday October 07, 2010 @07:10PM
(#1769888)
Why they have only two database servers running (with their database in memory, no less) with 200 million check-ins, is completely beyond me.
[ Parent
| on HN ]
Re:MongoDB's lead developer: Foursquare outage post mortem
by seiji on Thursday October 07, 2010 @07:19PM
(#1769915)
They are dealing with web scale sharded NoSQL realtime geo scala. Old rules don't apply when 80% of the words describing your company didn't exist two years ago.
Re:MongoDB's lead developer: Foursquare outage post mortem
by doty on Thursday October 07, 2010 @07:31PM
(#1769946)
I honestly cannot tell whether or not that comment was serious.
Re:MongoDB's lead developer: Foursquare outage post mortem
by epochwolf on Thursday October 07, 2010 @08:57PM
(#1770166)
Any comment with the words "web scale" should be considered a joke until proven otherwise. :)
Re:MongoDB's lead developer: Foursquare outage post mortem
by bl4k on Friday October 08, 2010 @12:29AM
(#1770617)
Just as I was thinking that this thread was getting worse the further I scroll down I come across the best summation of this story
Re:MongoDB's lead developer: Foursquare outage post mortem
by look_lookatme on Thursday October 07, 2010 @09:59PM
(#1770296)
I cracked up at this. Well played.
Re:MongoDB's lead developer: Foursquare outage post mortem
by mrkurt on Thursday October 07, 2010 @08:59PM
(#1770173)
They actually said 4. Two shards with slaves for redundancy. It was apparently working fine until they lost track of what was going on. :)
Re:MongoDB's lead developer: Foursquare outage post mortem
by marclove on Friday October 08, 2010 @07:26AM
(#1771250)
Yea but like you said, since half of them are just for redundancy, they were in effect only running 2 database servers. I must say I find it stunning that a service with that much traffic, especially one with an infrastructure that requires the entire database to be in-memory, would be operating with just 2 database servers running on EC2.
I know hindsight is 20/20, but I can't imagine the foresight was any worse than 20/30.