Hacker News new | past | comments | ask | show | jobs | submit login

TL;DR During updates, Mongo moves a record from one position in the index to another position. It does this in-place without acquiring a lock. Thus during a read query, the index scan can miss the record being updated, even if the record matched the query before the update began.



mongo developer 1

Man, it's just taking too damn long to run this update. What should we do?

mongo developer 2

Uh....remove all the locks?

mongo developer 1

Oh, yeah, that makes sense, let's do that.

mongo developer 3

Hey, what are you guys up to?

mongo developer 2

Making it web-scale!

mongo developer 3

Good job, keep it up!


Seriously. I was looking at DB usage statistics recently and was appalled MongoDB is still so popular. I thought it was done, nail in the coffin, when https://www.youtube.com/watch?v=b2F-DItXtZs came out 6 years ago, I haven't followed it much since then apart from the occasional post like this whose content is just "you thought it was bad already? haha it's worse."




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: