|MongoDB 1.8.0 Released||Eliot||3/16/11 12:26 PM|
MongoDB 1.8.0 has been released.
For details, please see:
Thanks for all the help along the way,
|Re: [mongodb-user] MongoDB 1.8.0 Released||Ofer Fort||3/16/11 3:47 PM|
That's great news, we've been waiting for this release (still using 1.6.5...) and looking forward to all it's new features and improvements.
A quick question though, we have been monitoring those two issues:http://groups.google.com/group/mongodb-user/browse_thread/thread/52a18b072aecb7ef/ and http://groups.google.com/group/mongodb-user/browse_thread/thread/92cea4e6df8b9c01/ since we have pretty big collections, and chunk splitting and replication are major issues for us.
Were they addressed in the release?
Thanks a lot for your hard work.
|Re: [mongodb-user] MongoDB 1.8.0 Released||Eliot||3/16/11 6:20 PM|
Those issues are pretty specific to single deployments at this point,
so I don't think those are general issues.
There were lots of improvements to splitting and balancing overall.
|Re: MongoDB 1.8.0 Released||ruby||3/16/11 11:53 PM|
Eliot Horowitz <eliothorowitz@...> writes:
hi, isn't this fix included in 1.8.0?
I find that this error still occurs in 1.8.0 windows x64
and still, upon reboot the mongod.lock file is not empty.
|Re: [mongodb-user] Re: MongoDB 1.8.0 Released||Eliot||3/16/11 11:56 PM|
No, it got pushed to 1.8.1, sorry for the confusion.
Will be in the 1.8 nightly tomorrow.