Re:MongoDB 2.0 Released
by rbranson on Monday September 12, 2011 @10:08PM
(#2989663)
The problem is: "a pending write lock acquisition will prevent further read lock acquisitions until fulfilled." Inserts aren't actually guaranteed to be in memory, as they're done in a file-backed memory region. A write and page fault can and frequently does cause a flush and hang while that lock is held, particularly as the hot dataset size increases relative to physical RAM.
[ Parent
| on HN ]
There are no comments on this comment yet.