3 ms·
It should be noted that this was not really a problem with MongoDB. Foursquare used a poorly-chosen shard key that caused a disproportionate load on one of its
by vannevar 15y ago
It should be noted that this was not really a problem with MongoDB. Foursquare used a poorly-chosen shard key that caused a disproportionate load on one of its shards, and on top of that did not have proper system monitoring in place to alert them that a server was running out of RAM. It should also be noted that no data was lost in the process of resolving the problem.
- latch 15y agoAnd both companies were extremely transparent about it and the community generally appreciated the way it was handled: https://groups.google.com/forum/#!topic/mongodb-user/UoqU8ofp134 https://groups.google.com/forum/#!topic/mongodb-user/UoqU8of...
- nikcub 15y agoI thought both Foursquare and 10gen handled the situation then very well, especially considering how much traction the story got (it had all the elements - a popular service, a popular new database, etc.) I was sort of suggesting that this anonymous post may have come from somebody at Foursquare, since what is described kinda matches what happen there. The 'politics' element could also match because of the common investor - but I see that both 10gen and 4sq have responded here saying that they do not know who wrote this - which I believe.