MongoDB 3.2.1 is released

61 views
Skip to first unread message

Ramon Fernandez

unread,
Jan 12, 2016, 9:38:49 AM1/12/16
to mongodb-...@googlegroups.com, mongodb-dev, mongod...@googlegroups.com, mongodb...@googlegroups.com
MongoDB 3.2.1 is out and is ready for production deployment. This release contains only fixes since 3.2.0, and is a recommended upgrade for all 3.2 users.

This release includes a critical fix for SERVER-21868: due to a logic error during regular shutdown, 3.2.0 replica set secondaries may mark certain replicated operations as successfully applied even though they have not been. This can leave a secondary node in an inconsistent state with respect to the primary and other secondaries. All MongoDB 3.2.0 nodes should be upgraded to 3.2.1.

For more details about this bug, affected versions and workarounds please see: https://jira.mongodb.org/browse/SERVER-21868

Also fixed in this release:
SERVER-21366   Long-running transactions in MigrateStatus::apply
SERVER-21724   Backup role can't read system.profile
SERVER-21750   getMore command does not set "nreturned" operation counter
SERVER-21772   findAndModify not captured by Profiler
SERVER-21792   75% performance regression in insert workload under Windows between 3.0.7 and 3.2 with WiredTiger
SERVER-21867   WiredTiger oplog cursor can return repeated segments
SERVER-21930   Restart oplog query if oplog entries are not monotonically increasing
SERVER-21971   Not possible to elect a primary if non-voting member is ahead (PV0)


As always, please let us know of any issues.

-- The MongoDB Team

Sicabol

unread,
Jan 12, 2016, 11:55:14 AM1/12/16
to mongodb-user, mongodb-...@googlegroups.com, mongo...@googlegroups.com, mongodb...@googlegroups.com
Hi,

thanks for the update. Apparently it's not yet available on the Ubuntu PPA.
Reply all
Reply to author
Forward
0 new messages