We're wrapping up development for 1.6.0 and could use all the help we
can get testing this release.
Depending on what we find, we'll be targeting 1.5.7 as the final 1.5.x
version for Tuesday or Wednesday next week, and release 1.6.0 either
Friday 7/30 or Monday 8/2.
Major features to test:
- Replica Sets : ready for testing. some loose ends we're still
fixing, but testers would be greatly appreciate
- Sharding : lots of stability/maturity improvements - testers would be great
Downloads: http://www.mongodb.org/downloads
Change Log: http://jira.mongodb.org/browse/SERVER/fixforversion/10179
For issues with replica sets and sharding, the best would be to report
them to http://jira.mongodb.org/ or
http://groups.google.com/group/mongodb-dev
Thanks for the help and support,
-Eliot
The change we made is that the slave does a long poll to the master so
changes should be more real time rather than less.
> --
> 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.
>
>
> db.printSlaveReplicationInfo()
source: 10.242.73.123
syncedTo: Wed Jul 28 2010 03:31:51 GMT+0000 (UTC)
= 43secs ago (0.01hrs)
- Ian
However, that still doesn't explain why I couldn't get a full resync to work with 1.5.6 as the master, unless the query blocks for 60 seconds even when behind. In that case, it would probably take a really really long time to get a resync to happen, right?
- Ian