Changes in MongoDB 3.0¶
- Release Notes for MongoDB 3.0
- Minor Releases
- 3.0 Changelog
- 3.0.15 – May 15, 2017
- 3.0.14 – Nov 4, 2016
- 3.0.13 – Oct 31, 2016
- 3.0.12 – May 9, 2016
- 3.0.11 – Mar 31, 2016
- 3.0.10 – Mar 8, 2016
- 3.0.9 – Jan 26, 2016
- 3.0.8 – Dec 15, 2015
- 3.0.7 – Oct 13, 2015
- 3.0.6 – August 24, 2015
- 3.0.5 – July 28, 2015
- 3.0.4 – June 16, 2015
- 3.0.3 – May 12, 2015
- 3.0.2 – April 9, 2015
- 3.0.1 – March 17, 2015
- Major Changes
- Replica Sets
- Sharded Clusters
- Security Improvements
- Improvements
- MongoDB Enterprise Features
- Additional Information
- Changes Affecting Compatibility
- Compatibility Changes in MongoDB 3.0
- Storage Engine
- Replication Changes
- MongoDB Tools Changes
- Sharded Cluster Setting
- Security Changes
- Indexes
- Driver Compatibility Changes
- General Compatibility Changes
findAndModify
Return Documentupsert:true
with a Dotted_id
Query- Deprecate Access to
system.indexes
andsystem.namespaces
- Collection Name Validation
- Platform Support
- Linux Package Repositories
- Removed/Deprecated Commands
- Date and Timestamp Comparison Order
- Server Status Output Change
- Unix Socket Permissions Change
cloneCollection
- Compatibility Changes in MongoDB 3.0
- Upgrade Process
- Upgrade MongoDB to 3.0
- Upgrade Recommendations and Checklists
- Upgrade MongoDB Processes
- Upgrade Existing
MONGODB-CR
Users to UseSCRAM-SHA-1
- General Upgrade Procedure
- Upgrade to SCRAM
- Downgrade MongoDB from 3.0
- Downgrade Recommendations and Checklist
- Downgrade MongoDB Processes
- Downgrade a Standalone
mongod
Instance - Downgrade a 3.0 Replica Set
- Downgrade a 3.0 Sharded Cluster
- Requirements
- Change Storage Engine to MMAPv1
- Change Shards to Use MMAPv1
- Change Config Servers to Use MMAPv1
- Disable the Balancer.
- Stop the last config server listed in the
mongos
’configDB
setting. - Export data of the second config server listed in the
mongos
’configDB
setting. - For the second config server, create a new data directory for MMAPv1.
- Restart the second config server with MMAPv1.
- Upload the exported data using
mongorestore
to the second config server. - Shut down the second config server.
- Restart the third config server.
- Export data of the third config server.
- For the third config server, create a new data directory for MMAPv1.
- Restart the third config server with MMAPv1.
- Upload the exported data using
mongorestore
to the third config server. - Export data of the first config server listed in the
mongos
’configDB
setting. - For the first config server, create data directory for MMAPv1.
- Restart the first config server with MMAPv1.
- Upload the exported data using
mongorestore
to the first config server. - Enable writes to the sharded cluster’s metadata.
- Re-enable the balancer.
- Downgrade Binaries
- Downgrade a Standalone
- General Downgrade Procedure
- Upgrade MongoDB to 3.0
- Download
- Changes Affecting Compatibility
- Minor Releases