MongoDB development release 1.5.0 is available

Eliot Horowitz

unread,

Apr 9, 2010, 12:03:59 PM4/9/10

to mongod...@googlegroups.com

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-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

kevin

unread,

Apr 9, 2010, 12:07:14 PM4/9/10

to mongod...@googlegroups.com

thanks! will this improve map/reduce performance?

--
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.

Eliot Horowitz

unread,

Apr 9, 2010, 12:11:43 PM4/9/10

to mongod...@googlegroups.com

In many cases yes.

kevin

unread,

Apr 9, 2010, 12:46:07 PM4/9/10

to mongod...@googlegroups.com

On Fri, Apr 9, 2010 at 9:03 AM, Eliot Horowitz <elioth...@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.

can you tell if anything is broken? i just have a single node, and i want to see faster map reduce..

is this a drop in upgrade or anything to be done for db directory?
thanks

Eliot Horowitz

unread,

Apr 9, 2010, 12:48:33 PM4/9/10

to mongod...@googlegroups.com

nothing that we know of is broken.
the build system runs the regression suite before pushing binaries.

its a drop in replacement

kevin

unread,

Apr 9, 2010, 12:50:45 PM4/9/10

to mongod...@googlegroups.com

if anything goes wrong, can i downgrade?

Kristina Chodorow

unread,

Apr 9, 2010, 12:56:12 PM4/9/10

to mongod...@googlegroups.com

Yes, it's a drop-in downgrade, too :)

kevin

unread,

Apr 9, 2010, 1:03:43 PM4/9/10

to mongod...@googlegroups.com

great, thanks.. just moved to 1.5, and no change in map reduce performance for me.... but everything is working great...

when i was moving, i got this error in my web app, is this new? earlier there was no error raised if the mongod was down? i am just collecting stats, and dont want error to raise in pymongo.. if mongod is down... is this possible?

raise AutoReconnect("could not connect to %r" % self.__nodes)
[warn] mod_fcgid: stderr: AutoReconnect: could not connect to [('app1', 37027)]

Kent Sibilev

unread,

Apr 9, 2010, 1:09:14 PM4/9/10

to mongod...@googlegroups.com

On Fri, Apr 9, 2010 at 12:03 PM, Eliot Horowitz <elioth...@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-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

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

Eliot Horowitz

unread,

Apr 9, 2010, 1:10:51 PM4/9/10

to mongod...@googlegroups.com

can you send the output of db.serverStatus()

Kristina Chodorow

unread,

Apr 9, 2010, 1:21:10 PM4/9/10

to mongod...@googlegroups.com

@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.

Brian Carpio

unread,

Apr 9, 2010, 2:31:48 PM4/9/10

to mongodb-user

Any switch we need to add to enable the tcp timout for pairing? Or is
this automatic?

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>

Eliot Horowitz

unread,

Apr 9, 2010, 2:32:32 PM4/9/10

to mongod...@googlegroups.com

brian: should be automatic.

> To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.

Brian Carpio

unread,

Apr 9, 2010, 2:34:05 PM4/9/10

to mongodb-user

Yep, just tested it looks like we fail over in about 30 seconds.

Thanks this is great!

Brian Carpio

On Apr 9, 12:32 pm, Eliot Horowitz <eliothorow...@gmail.com> wrote:
> brian: should be automatic.
>

Brian Carpio

unread,

Apr 9, 2010, 4:47:23 PM4/9/10

to mongodb-user

Ok it seems like this is taking 30-60 seconds.. do you know why it
takes so long.. is there a chance that in the future this can be a
configurable value?

Eliot Horowitz

unread,

Apr 9, 2010, 4:48:28 PM4/9/10

to mongod...@googlegroups.com

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

Brian Carpio

unread,

Apr 9, 2010, 5:13:17 PM4/9/10

to mongodb-user

Ok, Eric, thanks for the feedback its much appreciated!! Thanks for
the fix as well it will due for now.

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
>

Reply all

Reply to author

Forward