MongoDB 2.4 Released: Text Search, Security, Hash-based Sharding

[dmytton]

Using the new working set analyser is going to make figuring out how much memory you need significantly easier. Giving MongoDB enough memory for your working set is the easiest way to get performance but it was quite difficult to figure it out: you had to know both data and index sizes across your most common usage patterns.

[diminoten]

Do you know of any resources that give some info on this topic in general? I've been looking but I haven't found anything that's sufficiently plainly-spoken that I fully grasp the contents.

[badgar]

> you had to know both data and index sizes across your most common usage patterns.

This is called capacity planning. If you can't estimate what resources you use, I wouldn't expect great success scaling.

[gregjor]

Great to see the Pick database reinvented bit by bit. Takes me back to 1980. Forget the past, doomed to repeat, etc.

[newishuser]

Yeah, your right, MongoHQ hasn't brought anything positive to web development and there's no way they're going to make a business supporting their db. It definitely needs to be put in it's place and we should all take the time to talk about just how cool we are for predicting it's downfall. If only the whole world had enough insight to just stop before they tried to do something awesome. After all, someone may have tried it before.

[spf13]

While MongoDB was certainly built upon the shoulders of the giants that went before, so has been every product ever. To call it a reinvention of the Pick Database is flattering but highly inaccurate.

Perhaps more accurate is learn from the past, improve the future.

[julien_c]

Can you elaborate for those of use who weren't around in 1980?

[eddieroger]

My understanding of Pick databases was that they were typeless. Mongo isn't. There's a difference between being typeless and schemaless, and Mongo is a good mix for my usecases.

[redwood]

Reminds me of Bill Gates recent IAMA where he talked about how they were close but didn't make it to market with a similar product, e.g. he seemed to be saying "MSFT was there first...!" I guess not, if this has been around since 1980 :) http://www.reddit.com/r/IAmA/comments/18bhme/im_bill_gates_c...

[davidkellis]

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]

Collection 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

[c-oreills]

You can circumvent this in the short term by using one collection per db.

[Lionga]

It is great to have a stable version with fast count indexes see https://jira.mongodb.org/browse/SERVER-1752

Best feature for me

[friendly_chap]

They are not fast, they are "normal speed" now. They were slow before. That was one of the problems which made me question the competency of the Mongo team.

Best feature for me too anyway.

[c-oreills]

"db.killOp() Can Now Kill Foreground Index Builds"

That's going to save a lot of accidental "shit-the-whole-db-is-locked" pain.

[dkhenry]

I am curious to play with the text searching. I wonder how it stacks up to Lucerne or Solr in the text indexing space

[ecaron]

The MongoDB staff had said they're mostly adding text searching to satisfy a repeat request that they've heard over and over - but they've said that anyone really wanting to do text searching at scale should use something like Sphinx, Solr or ElasticSearch.

[tbrock]

Keep in mind that it is both new and experimental.

If you are comparing them based on functionality and performance you are missing the point.

It is my opinion that this easily bests external implementations by reducing moving parts and removing the asynchronous nature of the updates to search indexes.

The text index is updated atomically and in real time. Best of all: it's not another part of your stack that needs to be setup and maintained.

[mumrah]

I am quite sure it will not come close to Lucene/Solr in terms of performance or capabilities.

[leothekim]

According to the upgrade instructions [1], the only supported upgrade path from sharded 2.0 clusters is via 2.2.

[1] http://docs.mongodb.org/manual/release-notes/2.4-upgrade/#up...

[c-oreills]

And infact you can't have a mix of 2.2 and 2.4 boxes in the same cluster, you have to go via 2.2.1

[derricki]

I was hoping the security enhancements would include SSL certificate validation. Anyone know why they don't do that, or how a user should approach that limitation?

[matthewlucid]

We'll be moving away from MongoDB because it doesn't support certificate validation. What is the point of SSL connections if you don't validate the certificate? It seems that you get all the drawbacks of encryption (overhead, throughput) with none of the benefits (security).

I'd love to see a solution.

[milkie]

SSL certificate validation is in the 2.4 release.

[jonesjim]

Whoop! Multithreaded javascript with V8 JavaScript engine!

[apendleton]

I can't actually find any details about how this works in practice. Are multiple maps and reduces in a map-reduce executed simultaneously within a single mongod process? If so, how many? Is it based on the number of cores in the server?

Edit: not asking you specifically, just generally curious.

[vailripper]

Love seeing the text indexing!

[ranman]

V8 is another important change that isn't really touted much in this release.

[tbrock]

Yeah, this is a big deal. It enables very interesting opportunities to create a map reduce engine that isn't awful or which requires Java.

People use Hadoop because they have to, not because it is great. Isn't it time for a better alternative now that the toothpaste is out of the tube re: map/reduce?

Java doesn't even have hash literal syntax! Why would you ever want to query document oriented data with it as your language of expression?

[leif]

I'm glad this is out. I'm really going to enjoy plugging fractal trees in under FTS.

[dschiptsov]

any row-level locking?)

[L0j1k]

[Comment about supporting only one master]