MongoDB 3.1.0 is released

563 views
Skip to first unread message

Ramon Fernandez

unread,
Mar 17, 2015, 6:21:15 PM3/17/15
to mongo...@googlegroups.com
MongoDB 3.1.0 has been released. As a reminder, 3.1.0 is a development release and is not intended for production use. The 3.1 series will evolve into 3.2, which will be for production.

New/fixed in this release:
SERVER-17121   Throughput Dropout on mongo-sim insert-update-query workload with WiredTiger
SERVER-17141   session->truncate failed with File Not Found in WiredTigerRecordStoreThread for local.oplog.rs
SERVER-17193   Disable capped collection tests in small_oplog* test suites
SERVER-17195   WiredTiger: highly contended write traffic may lock collection
SERVER-17206   WT Secondaries fall behind on heavy insert workload but MMAPv1 secondaries don't
SERVER-17241   Inserting a broken polygon into a "2dsphere" index crashes MongoDB
SERVER-17250   logOp rollback when legacy insert creates a namespace and then fails to insert the document (fatal assertion)
SERVER-17281   Segfault during id_hack FSM test
SERVER-17299   Extraneous memory allocations in snappy hurt WiredTiger performance on Windows
SERVER-17344   RC9/wiredTiger batched insert performance regression
SERVER-17345   WiredTiger -> session.truncate: the start cursor position is after the stop cursor position
SERVER-17372   FindAndModify no longer returns "value" if upsert results in an insert and "new" is false
SERVER-17416   Deadlock between MMAP V1 journal lock and oplog collection lock
SERVER-17487   cloner dropDups removes _id entries belonging to other records
SERVER-17499   Using eval command to run getMore on aggregation cursor trips fatal assertion
SERVER-17501   Increase journalling capacity limits
SERVER-17506   Race between inserts and checkpoints can lose records under WiredTiger
SERVER-17510   "Didn't find RecordId in WiredTigerRecordStore" on collections after an idle period
SERVER-17515   copyDatabase fails to replicate indexes to secondary

If you have any questions please let us know.

-- The MongoDB Team
Reply all
Reply to author
Forward
0 new messages