New in version 3.0.0
March 6th, 2015
- 7-10x Better Performance:
- The new WiredTiger storage engine in MongoDB 3.0 delivers 7-10x greater throughput for write-intensive applications with more granular document-level concurrency control. This translates to massive performance gains with less hardware for write-heavy projects such as your next IoT, customer data management, social, and mobile apps.
- Up to 80% Less Storage:
- MongoDB now supports native compression, allowing you to reduce your physical storage footprint by up to as much as 80%. You have the added flexibility to choose between different compression algorithms to optimize for performance and storage efficiency, depending on your apps needs.
- With more granular concurrency control and built-in compression, MongoDB 3.0 lets you simplify your architecture, allowing you to do far more with less hardware.
- Reduce Operational Overhead By Up to 95%:
- Ops Manager is the best way to run MongoDB. This solution makes routine tasks as easy as pushing a button and eliminates previously manual and time consuming tasks involved in managing MongoDB. You can now deploy, monitor, back up and scale MongoDB with ease.
- Pluggable Storage Optimized For Your Workload:
- We understand that with an increasingly complex landscape of data-driven apps, a “one size fits all” approach to storage doesn’t cut it anymore. That’s why MongoDB 3.0 includes a pluggable storage engine API to extend the database with new capabilities.
- Low Latency Across the Globe:
- Today's leading applications are global and serve always-connected audiences that demand instant gratification. With MongoDB, you can now easily distribute up to 50 MongoDB replicas closer to your users all over the world, reducing the effects of network latency and providing a better user experience.
- Enhancements That Make You More Productive:
- MongoDB 3.0 includes a number of operational improvements to the MongoDB Query Language as well as the tools included with the database. They include...
- Faster Loading and Export. Data can be loaded and extracted at higher speed and with greater efficiency using MongoDB’s revised multi-threaded mongoimport, mongoexport, mongodump, mongorestore and mongooplog tools.
- Easier Query Optimization. Better understand query performance with the new explain() method. It is now possible to calculate and review query plans without first running the query. The query plan can be applied to a broader set of query types, and error handling is improved.
- Faster Debugging. You now have much greater control over the granularity of log messages and specific functional areas of the server to more precisely investigate issues. You can configure which specific components of the database should be exposed for higher definition logging and add severity levels for each log message.
- Richer Geospatial Apps. With the addition of big polygon selections, MongoDB’s geospatial support is extended to include multi-hemisphere queries that can span more than 50% of the earth’s surface. For example, an airline can now run queries to identify all aircrafts that have traveled across multiple hemispheres in the past 24 hours.
- Better Time-Series Analytics. Developers can construct richer time-series analytics queries with less code using the aggregation framework’s new $dateToString operator.
- Ensure Regulatory and Internal Compliance:
- MongoDB 3.0 adds to the existing security capabilities of the database with a more robust auditing framework.
- Auditing now extends beyond capturing administrative actions (i.e. schema operations, authentication and authorization activities) to include the logging of read and write (DML) operations to the database. You can construct and filter audit trails for any operation against MongoDB without having to rely on third-party tools. 3.0 also features the introduction of role-based auditing. Auditing is available as part of MongoDB Enterprise Advanced.
New in version 2.6.7 (January 22nd, 2015)
- Decreased mongos memory footprint when shards have several tags SERVER-16683
- Removed check for shard version if the primary server is down SERVER-16237
- Fixed: /etc/init.d/mongod startup script failure with dirname message SERVER-16081
- Fixed: mongos can cause shards to hit the in-memory sort limit by requesting more results than needed SERVER-14306
- All issues closed in 2.6.7
New in version 2.6.5 (October 17th, 2014)
- $rename now uses correct dotted source paths SERVER-15029
- Partially written journal last section does not affect recovery SERVER-15111
- Explicitly zero .ns files on creation SERVER-15369
- Plan ranker will no longer favor intersection plans if predicate generates empty range index scan SERVER-14961
- Generate Community and Enterprise packages for SUSE 11 SERVER-10642
- All issues closed in 2.6.5
New in version 2.5.5 (February 5th, 2014)
- New write operation method for insert, update, remove
- Bug fixes:
- SNMP Agent does not start
- Add module suite support to smoke.py
New in version 2.5.4 (January 13th, 2014)
- Add option to compact command to leave in padding
- User defined roles
- Server automatically abort queries/commands after user-specified time limit
New in version 2.4.9 (January 11th, 2014)
- Bug fixes:
- misplaced openssl callback registration can cause crashes
- clang compiled mongo shell crashes on exit with a stack trace in v8
- logging in ~ReplicaSetMonitor() crashes
- Non-numeric expiresAfterSeconds causes bad TTL query
- Shell stops working after long autocomplete operation
- Failure to rollback usePowerOf2Sizes should not cause fatal error
- SERVER-11869 Support for non-client opTime in mongod GLE
- $where inside of projection $elemMatch causes segmentation fault
- Passing $where predicate to db.currentOp() crashes mongod
- Cannot set false setParameter options in config file
- textIndexVersion compatibility check not complete
- writeback listener may not get correct code back from ClientInfo::getLastError
- Mongos cannot do slaveOk queries when primary is down
- New sharded connections to a namespace trigger setShardVersion on all shards
- retry logic for read preferences should also apply on lazy recv() network failure
- slaveok versioning logic in mongos should also apply to read prefs
- Modifying collection options can cause restores of collection to fail
New in version 2.4.8 (December 5th, 2013)
- Increase future compatibility for 2.6 authorization features
- Fix dbhash cache issue for config servers