4 ms·
I was hoping for collection-level locking to be a part of the 2.4 release. I didn't see any mention of it in the release notes. Last I heard they were going to
by davidkellis 14y ago
I was hoping for collection-level locking to be a part of the 2.4 release. I didn't see any mention of it in the release notes. Last I heard they were going to implement collection-level locking and then begin work on document-level locking. I'm still hoping document-level locking isn't too far off.
- spf13 14y agoCollection level locking isn't in 2.4. Working on more granular locking for 2.6/2.8. May skip collection level entirely for something more granular. More details can be found in the collection level locking ticket https://jira.mongodb.org/browse/SERVER-1240 https://jira.mongodb.org/browse/SERVER-1240
- davidkellis 14y agoSkipping collection level locking and going for something more granular (like document level) would be awesome.
- tomsthumb 14y agoDon't you pretty much get document level locking by using multiple $<update> modifiers in a single query?
- apendleton 14y agoFrom an atomicity perspective, yes. From a performance perspective, no; other concurrent operations affecting anything else on the whole database wait on your write.
- c-oreills 14y agoYou can circumvent this in the short term by using one collection per db.
- camus 14y agoyou mean one document per collection.