Cassandra vs MongoDB For Time Series Data

Re:Cassandra vs MongoDB For Time Series Data by snmaynard on Wednesday August 21, 2013 @05:12PM (#6253340)

> Implications: if you run a query in production that doesn't hit an index, all traffic stops

Even if Mongo did have a global write lock, which it doesn't as has already been covered, it yields on page faults which means that other queries are minimally impacted. See: http://docs.mongodb.org/manual/faq/concurrency/#does-a-read-...

[ Parent | on HN ]

Re:Cassandra vs MongoDB For Time Series Data by arohner on Wednesday August 21, 2013 @06:01PM (#6253598)

Mongo does have a global write lock. A per-db lock does me very little good when I only have one DB.

As to your linked doc, emphasis added:

> In some situations, read and write operations can yield their locks.

> Long running read and write operations, such as queries, updates, and deletes, yield under many conditions.

In practice, I've been bitten hard by this. A new feature rolls out, and users can't log in anymore, because a query is taking 2 minutes to run.

[ Parent | on HN ]

Re:Cassandra vs MongoDB For Time Series Data by cbsmith on Wednesday August 21, 2013 @08:35PM (#6254306)

That's solves the contention problem, but just by virtue of yields on page faults being a big feature you can see where Mongo does have some scaling issue.

[ Parent | on HN ]