Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MongoDB 2.2.0 Released

mongodb.org

Post reply on HN
Print view View original

41–50 of 64 posts

Re: MongoDB 2.2.0 Released

#42

Post by mtkd »

cmer wrote: post #5

My experience with MongoDB hasn't been the most pleasant in a write-heavy environment. Until they fix the write lock properly, MongoDB is pretty much useless for many high throughput applications in my opinion... The new DB level locking introduced in this release is a joke. There's not much difference between that and the old global write lock unless you split your database in dozens of smaller ones. What a pain. I…

The problems with early rev SQL servers were similar (in inconvenience) but, with feedback from users and hard work from developers, they soon moved beyond MVP.

I'm willing to suck up some inconvenience with MongoDB, it's one of the most inspiring technologies of the last decade. Web application persistance feels more like a fully connected limb now.

I can understand the gripes but do urge people to give 10gen some slack and appreciate that what they are building takes time - it's clear that the team are working hard on features driven by community feedback.

Re: MongoDB 2.2.0 Released

#46

Post by cmer »

mtkd wrote: post #42
cmer wrote: post #5

My experience with MongoDB hasn't been the most pleasant in a write-heavy environment. Until they fix the write lock properly, MongoDB is pretty much useless for many high throughput applications in my opinion... The new DB level locking introduced in this release is a joke. There's not much difference between that and the old global write lock unless you split your database in dozens of smaller ones. What a pain. I…

The problems with early rev SQL servers were similar (in inconvenience) but, with feedback from users and hard work from developers, they soon moved beyond MVP. I'm willing to suck up some inconvenience with MongoDB, it's one of the most inspiring technologies of the last decade. Web application persistance feels more like a fully connected limb now. I can understand the gripes but do urge people to give 10gen some s…

It's more than inconvenience when your whole service is down because some database queries take up to 30 seconds to complete (and often time out), and when replication on some servers is days behind (and some are up to date). We also had to completely flush our data a few times because of some corruption we couldn't recover from.

The truth is, MongoDB is awesome if your dataset fits in memory, but if you're in a write-intensive environment with 400-500GB of data, it's just not there yet.

Re: MongoDB 2.2.0 Released

#47

Post by nosequel »

crcsmnky wrote: post #41
Ricapar wrote: post #16

Still no support for Solaris on SPARC! :(

I'm not trolling you when I ask this, I'm simply curious. Of the open source projects you follow, how many still do builds for Solaris? How often do you have to build them yourself?

Lots of big companies, mostly infrastructure like telecom or tv, use Solaris still. Unless the project aims to support those uses, it usually isn't worth their time.

Re: MongoDB 2.2.0 Released

#48

Post by cagenut »

ranman wrote: post #4

Awesome release, notes summary: • Aggregation Framework to fix some map-reduce woes. • TTL Collections • DB Level Locking (A step in the right direction) • Better yielding on page faults • Tag aware sharding (HELL YES) • Better Read Prefs • Indexes now handled by mongodump/mongorestore • mongooplog replay is awesome for getting point in time backups • Shell now has full unicode, multiline command history, $EDITOR sup…

could you go into why tag aware sharding is a "HELL YES" for you? I was kindof already of the opinion that mongo sharding is much too complicated (http://i.imgur.com/c3Dpq.jpg), this seems to compound that. Is it something you've needed/wanted so bad that its worth it?

Re: MongoDB 2.2.0 Released

#49

Post by eckyptang »

tommoor wrote: post #28
cmer wrote: post #9

Earlier quoted context omitted.

That's good to know. It still feels like an half-assed solution to a very serious problem, however. I definitely won't be looking at MongoDB again until this is fixed for good, and until I know replication is more reliable. Had terrible problems that that too unfortunately.

It's not half-assed so much as a first step. 10gen have previously stated that the plan is to gradually increase the granularity or write-locks over successive releases.

Until they end up with MVCC...

Re: MongoDB 2.2.0 Released

#50

Post by dmytton »

cmer wrote: post #46
mtkd wrote: post #42

Earlier quoted context omitted.

The problems with early rev SQL servers were similar (in inconvenience) but, with feedback from users and hard work from developers, they soon moved beyond MVP. I'm willing to suck up some inconvenience with MongoDB, it's one of the most inspiring technologies of the last decade. Web application persistance feels more like a fully connected limb now. I can understand the gripes but do urge people to give 10gen some s…

It's more than inconvenience when your whole service is down because some database queries take up to 30 seconds to complete (and often time out), and when replication on some servers is days behind (and some are up to date). We also had to completely flush our data a few times because of some corruption we couldn't recover from. The truth is, MongoDB is awesome if your dataset fits in memory, but if you're in a writ…

Not true. We're processing 12TB of data each month with thousands of writes per second and sub-millisecond response times. You simply have to understand how to use MongoDB correctly which isn't difficult with the out of the box settings and by reading some of the documentation. Figuring out your working set is the most difficult part but that doesn't take long to calculate based on understanding the queries you're doing and creating the appropriate indexes.

Since you seem to be fairly negative about MongoDB but light on details, perhaps you should write up your experiences so others can learn from what you did wrong.

Post reply on HN