Notable Changes:
- real time replication
- block until write replicated to N servers:
http://www.mongodb.org/display/DOCS/Replication#Replication-BlockingforReplication
- btree split optimization
- better repl pair failure detection
- map reduce locking/speed improvement
- distinct & group speed improvements
- ipv6 and unix socket support
- max radius on $near for geo
Download: http://www.mongodb.org/display/DOCS/Downloads
Change Log: http://jira.mongodb.org/browse/SERVER/fixforversion/10125
As always, please let us know of any issues,
-Eliot
--
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To post to this group, send email to mongod...@googlegroups.com.
To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.
The first release in the 1.5 development cycle is available for testing.
This is a development release so not recommended for production.
its a drop in replacement
Just migrated from 1.4.0 to 1.5.0 and now mongodb process takes 150M
of resident RAM instead of 19M on my MacOSX Snow Leopard. Is it
something to be expected?
--
Kent
Brian Carpio
On Apr 9, 11:21 am, Kristina Chodorow <krist...@10gen.com> wrote:
> @kevin the python driver was probably trying to use a socket that had been
> connected to your 1.4 mongod and couldn't reconnect to it (since it's not
> running anymore). A disconnect/reconnect should take care of it.
>
> On Fri, Apr 9, 2010 at 1:10 PM, Eliot Horowitz <eliothorow...@gmail.com>wrote:
>
> > can you send the output of db.serverStatus()
>
> > On Fri, Apr 9, 2010 at 1:09 PM, Kent Sibilev <ksr...@gmail.com> wrote:
> > > On Fri, Apr 9, 2010 at 12:03 PM, Eliot Horowitz <eliothorow...@gmail.com>
> > wrote:
> > >> The first release in the 1.5 development cycle is available for testing.
> > >> This is a development release so not recommended for production.
>
> > >> Notable Changes:
> > >> - real time replication
> > >> - block until write replicated to N servers:
>
> >http://www.mongodb.org/display/DOCS/Replication#Replication-Blockingf...
> > >> - btree split optimization
> > >> - better repl pair failure detection
> > >> - map reduce locking/speed improvement
> > >> - distinct & group speed improvements
> > >> - ipv6 and unix socket support
> > >> - max radius on $near for geo
>
> > > Just migrated from 1.4.0 to 1.5.0 and now mongodb process takes 150M
> > > of resident RAM instead of 19M on my MacOSX Snow Leopard. Is it
> > > something to be expected?
>
> > > --
> > > Kent
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > "mongodb-user" group.
> > > To post to this group, send email to mongod...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > mongodb-user...@googlegroups.com<mongodb-user%2Bunsu...@googlegroups.com>
> > .
> > > For more options, visit this group at
> >http://groups.google.com/group/mongodb-user?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "mongodb-user" group.
> > To post to this group, send email to mongod...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > mongodb-user...@googlegroups.com<mongodb-user%2Bunsu...@googlegroups.com>
> To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
Thanks this is great!
Brian Carpio
On Apr 9, 12:32 pm, Eliot Horowitz <eliothorow...@gmail.com> wrote:
> brian: should be automatic.
>
Brian Carpio
On Apr 9, 2:48 pm, Eliot Horowitz <eliothorow...@gmail.com> wrote:
> it will improved and possibly configurable with replica sets.
> this is the best we can do quickly - the real fix will be coming with repl. sets
>