Kelsey T Schubert
unread,Jan 24, 2018, 12:15:33 PM1/24/18Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to mongodb-...@googlegroups.com, mongod...@googlegroups.com, mongo...@googlegroups.com, mongodb...@googlegroups.com
MongoDB 3.4.11-rc0 is out and is ready for testing. This is a release candidate containing only fixes since 3.4.10. The next stable release 3.4.11 will be a recommended upgrade for all 3.4 users.
Fixed in this release:
- SERVER-19605 Oplog timeout should be configurable
- SERVER-19919 Chunks that exceed 250000 docs but are under half chunk size get marked as jumbo
- SERVER-21011 Certain queries against compound 2d/text indexes are incorrectly covered, return incorrect results
- SERVER-29293 Recipient shard fails to abort migration on stepdown
- SERVER-29921 Mongo connection uri doesn't support @ character in database name
- SERVER-30449 ProjectionSpecValidator is O(N**2) in number of fields in the projection
- SERVER-31101 WT table not dropped after collection is dropped due to long-running OperationContext
- SERVER-31225 The mongod process forks before listening for connections
- SERVER-32001 unindexing a key in a partial unique index may cause server crash
- SERVER-32048 Updates using a numeric path component may cause index entries not to be created
- SERVER-32286 Remove Type=forking from Debian SystemD service file
- WT-3079 Make sure eviction visits all trees
All Issues |
Downloads
As always, please let us know of any issues.
-- The MongoDB Team