• Release Notes >
• Release Notes for MongoDB 2.6

Release Notes for MongoDB 2.6

April 8, 2014

MongoDB 2.6 is now available. Key features include aggregation enhancements, text-search integration, query-engine improvements, a new write-operation protocol, and security enhancements.

Minor Releases

• 2.6 Changelog
  • 2.6.12 Changelog
    • Security
    • Sharding
    • Query
    • Write Operations
    • Storage
      • MMAP
    • Operations
    • Build and Packaging
    • Internals
  • 2.6.11 – Changes
    • Querying
    • Replication
    • Sharding
    • Indexing
    • Networking
    • Build and Testing
  • 2.6.10 – Changes
    • Security
    • Querying
    • Replication
    • Sharding
    • Storage
    • Indexing
    • Write Ops
    • Networking
    • Build and Packaging
    • Shell
    • Testing
  • 2.6.9 – Changes
    • Security
    • Querying
    • Replication and Sharding
    • Storage
    • Aggregation Framework
    • Build and Platform
    • Diagnostics and Internal Code
  • 2.6.8 – Changes
    • Security and Networking
    • Query and Aggregation
    • Replication
    • Sharding
    • Storage
    • Tools
    • Build and Packaging
    • Usability
    • Testing
  • 2.6.7 – Changes
    • Stability
    • Querying
    • Replication
    • Sharding
    • Packaging
  • 2.6.6 – Changes
    • Security
    • Stability
    • Querying
    • Replication
    • Sharding
    • Storage
    • Indexing and write Operations
    • Data Aggregation
    • Build and Packaging
    • Logging and Diagnostics
    • Testing and Internals
  • 2.6.5 – Changes
    • Security
    • Stability
    • Querying
    • Replication
    • Sharding
    • Storage
    • Indexing
    • Write Operations
    • Data Aggregation
    • Packaging
    • Logging and Diagnostics
    • Internal Code and Testing
  • 2.6.4 – Changes
    • Security
    • Querying
    • Replication
    • Sharding
    • Storage
    • Indexing
    • Write Ops
    • Networking
    • Geo
    • Text Search
    • Tools
    • Admin
    • Packaging
    • JavaScript
    • Shell
    • Usability
    • Logging and Diagnostics
    • Testing
  • 2.6.3 – Changes
  • 2.6.2 – Changes
    • Security
    • Querying
    • Geospatial
    • Write Operations
    • Replication
    • Sharding
    • Map/Reduce
    • Storage
    • Build and Packaging
    • Diagnostics
    • Administration
    • Tools
    • Shell
    • Internal Code
    • Testing
  • 2.6.1 – Changes
    • Stability
    • Build and Packaging
    • Querying
    • Geospatial
    • Replication
    • Sharding
    • Security
    • Write Operations

2.6.12 – Mar 24, 2016

• Fixed issue with MMAPv1 journaling where the “last sequence number” file (lsn file) may be ahead of what is synced to the data files: SERVER-22261.
• Fixed issue that permitted the creation of new role with the same name as a built-in role: SERVER-19284.
• Fixed issue where some index operations running during an active migration may cause the migration operation to skip some documents: SERVER-22535.
• All issues closed in 2.6.12

2.6.11 – Aug 12, 2015

• Improvements to query plan ranking SERVER-17815
• Improved ability for mongos to detect replica set failover and correctly route read operations to the new primary SERVER-18280
• Improved reporting of queries in getMore operation in db.currentOp() and the database profiler SERVER-16265
• All issues closed in 2.6.11

2.6.10 – May 19, 2015

• Improve user cache invalidation enforcement on mongos SERVER-11980
• Provide correct rollbacks for collection creation SERVER-18211
• Allow user inserts into the system.profile collection SERVER-18211
• Fix to query system to ensure non-negation predicates get chosen over negation predicates for multikey index bounds construction SERVER-18364
• All issues closed in 2.6.10

2.6.9 – March 24, 2015

• Resolve connection handling related crash with mongos instances SERVER-17441
• Add server parameter to configure idle cursor timeout SERVER-8188
• Remove duplicated (orphan) documents from aggregation pipelines with _id queries in sharded clusters SERVER-17426
• Fixed crash in geoNear queries with multiple 2dsphere indexes SERVER-14723
• All issues closed in 2.6.9

2.6.8 – February 25, 2015

• Add listCollections command functionality to 2.6 shell and client SERVER-17087
• copydb/clone commands can crash the server if a primary steps down SERVER-16599
• Secondary fasserts trying to replicate an index SERVER-16274
• Query optimizer should always use equality predicate over unique index when possible SERVER-15802
• All issues closed in 2.6.8

2.6.7 – January 13, 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

2.6.6 – December 09, 2014

• Fixed: Evaluating candidate query plans with concurrent writes on same collection may crash mongod SERVER-15580
• Fixed: 2.6 mongod crashes with segfault when added to a 2.8 replica set with 12 or more members SERVER-16107
• Fixed: $regex, $in and $sort with index returns too many results SERVER-15696
• Change: moveChunk will fail if there is data on the target shard and a required index does not exist. SERVER-12472
• Primary should abort if encountered problems writing to the oplog SERVER-12058
• All issues closed in 2.6.6

2.6.5 – October 07, 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

2.6.4 – August 11, 2014

• Fix for text index where under specific circumstances, in-place updates to a text-indexed field may result in incorrect/incomplete results SERVER-14738
• Check the size of the split point before performing a manual split chunk operation SERVER-14431
• Ensure read preferences are re-evaluated by drawing secondary connections from a global pool and releasing back to the pool at the end of a query/command SERVER-9788
• Allow read from secondaries when both audit and authorization are enabled in a sharded cluster SERVER-14170
• All issues closed in 2.6.4

2.6.3 – June 19, 2014

• Equality queries on _id with projection may return no results on sharded collections SERVER-14302.
• Equality queries on _id with projection on _id may return orphan documents on sharded collections SERVER-14304.
• All issues closed in 2.6.3.

2.6.2 – June 16, 2014

• Query plans with differing performance can tie during plan ranking SERVER-13675.
• mongod may terminate if x.509 authentication certificate is invalid SERVER-13753.
• Temporary map/reduce collections are incorrectly replicated to secondaries SERVER-13981.
• mongos incorrectly targets multiple shards for nested field shard key predicates SERVER-14138.
• rs.stepDown() during mapReduce causes fassert when writing to op log SERVER-14186.

• All issues closed in 2.6.2.

2.6.1 – May 5, 2014

• Fix to install MongoDB service on Windows with the --install option SERVER-13515.
• Allow direct upgrade from 2.4.x to 2.6.0 via yum SERVER-13563.
• Fix issues with background index builds on secondaries: SERVER-13589 and SERVER-13620.
• Redact credential information passed as startup options SERVER-13644.
• 2.6.1 Changelog.
• All issues closed in 2.6.1.

Major Changes

The following changes in MongoDB affect both the standard and Enterprise editions:

Aggregation Enhancements

The aggregation pipeline adds the ability to return result sets of any size, either by returning a cursor or writing the output to a collection. Additionally, the aggregation pipeline supports variables and adds new operations to handle sets and redact data.

• The db.collection.aggregate() now returns a cursor, which enables the aggregation pipeline to return result sets of any size.
• Aggregation pipelines now support an explain operation to aid analysis of aggregation operations.
• Aggregation can now use a more efficient external-disk-based sorting process.
• New pipeline stages:
  • $out stage to output to a collection.
  • $redact stage to allow additional control to accessing the data.
• New or modified operators:
  • set expression operators.
  • $let and $map operators to allow for the use of variables.
  • $literal operator and $size operator.
  • $cond expression now accepts either an object or an array.

Text Search Integration

Text search is now enabled by default, and the query system, including the aggregation pipeline $match stage, includes the $text operator, which resolves text-search queries.

MongoDB 2.6 includes an updated text index format and deprecates the text command.

Insert and Update Improvements

Improvements to the update and insert systems include additional operations and improvements that increase consistency of modified data.

• MongoDB preserves the order of the document fields following write operations except for the following cases:
  • The _id field is always the first field in the document.
  • Updates that include renaming of field names may result in the reordering of fields in the document.
• New or enhanced update operators:
  • $bit operator supports bitwise xor operation.
  • $min and $max operators that perform conditional update depending on the relative size of the specified value and the current value of a field.
  • $push operator has enhanced support for the $sort, $slice, and $each modifiers and supports a new $position modifier.
  • $currentDate operator to set the value of a field to the current date.
• The $mul operator for multiplicative increments for insert and update operations.

See also

Update Operator Syntax Validation

New Write Operation Protocol

A new write protocol integrates write operations with write concerns. The protocol also provides improved support for bulk operations.

MongoDB 2.6 adds the write commands insert, update, and delete, which provide the basis for the improved bulk insert. All officially supported MongoDB drivers support the new write commands.

The mongo shell now includes methods to perform bulk-write operations. See Bulk() for more information.

See also

Write Method Acknowledgements

MSI Package for MongoDB Available for Windows

MongoDB now distributes MSI packages for Microsoft Windows. This is the recommended method for MongoDB installation under Windows.

Security Improvements

MongoDB 2.6 enhances support for secure deployments through improved SSL support, x.509-based authentication, an improved authorization system with more granular controls, as well as centralized credential storage, and improved user management tools.

Specifically these changes include:

• A new authorization model that provides the ability to create custom User-Defined Roles and the ability to specify user privileges at a collection-level granularity.
• Global user management, which stores all user and user-defined role data in the admin database and provides a new set of commands for managing users and roles.
• x.509 certificate authentication for client authentication as well as for internal authentication of sharded cluster and/or replica set members. x.509 authentication is only available for deployments using SSL.
• Enhanced SSL Support:
  • Rolling upgrades of clusters to use SSL.
  • MongoDB Tools support connections to mongod and mongos instances using SSL connections.
  • Prompt for passphrase by mongod or mongos at startup.
  • Require the use of strong SSL ciphers, with a minimum 128-bit key length for all connections. The strong-cipher requirement prevents an old or malicious client from forcing use of a weak cipher.
• MongoDB disables the http interface by default, limiting network exposure. To enable the interface, see enabled.

See also

New Authorization Model, SSL Certificate Hostname Validation, and Security Checklist.

Query Engine Improvements

• MongoDB can now use index intersection to fulfill queries supported by more than one index.
• Index Filters to limit which indexes can become the winning plan for a query.
• Query Plan Cache Methods methods to view and clear the query plans cached by the query optimizer.
• MongoDB can now use count() with hint(). See count() for details.

Improvements

Geospatial Enhancements

• 2dsphere indexes version 2.
• Support for MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection.
• Support for geospatial query clauses in $or expressions.

See also

2dsphere Index Version 2, $maxDistance Changes, Deprecated $uniqueDocs, Stronger Validation of Geospatial Queries

Index Build Enhancements

• Background index build allowed on secondaries. If you initiate a background index build on a primary, the secondaries will replicate the index build in the background.

• Automatic rebuild of interrupted index builds after a restart.

  • If a standalone or a primary instance terminates during an index build without a clean shutdown, mongod now restarts the index build when the instance restarts. If the instance shuts down cleanly or if a user kills the index build, the interrupted index builds do not automatically restart upon the restart of the server.
  • If a secondary instance terminates during an index build, the mongod instance will now restart the interrupted index build when the instance restarts.

  To disable this behavior, use the --noIndexBuildRetry command-line option.

• ensureIndex() now wraps a new createIndex command.

• The dropDups option to ensureIndex() and createIndex is deprecated.

See also

Enforce Index Key Length Limit

Enhanced Sharding and Replication Administration

• New cleanupOrphaned command to remove orphaned documents from a shard.
• New mergeChunks command to combine contiguous chunks located on a single shard. See mergeChunks and Merge Chunks in a Sharded Cluster.
• New rs.printReplicationInfo() and rs.printSlaveReplicationInfo() methods to provide a formatted report of the status of a replica set from the perspective of the primary and the secondary, respectively.

Configuration Options YAML File Format

MongoDB 2.6 supports a YAML-based configuration file format in addition to the previous configuration file format. See the documentation of the Configuration File for more information.

Operational Changes

Storage

usePowerOf2Sizes is now the default allocation strategy for all new collections. The new allocation strategy uses more storage relative to total document size but results in lower levels of storage fragmentation and more predictable storage capacity planning over time.

To use the previous exact-fit allocation strategy:

• For a specific collection, use collMod with usePowerOf2Sizes set to false.

• For all new collections on an entire mongod instance, set newCollectionsUsePowerOf2Sizes to false.

  New collections include those: created during initial sync, as well as those created by the mongorestore and mongoimport tools, by running mongod with the --repair option, as well as the restoreDatabase command.

See /core/storage for more information about MongoDB’s storage system.

Networking

• Removed upward limit for the maxIncomingConnections for mongod and mongos. Previous versions capped the maximum possible maxIncomingConnections setting at 20,000 connections.
• Connection pools for a mongos instance may be used by multiple MongoDB servers. This can reduce the number of connections needed for high-volume workloads and reduce resource consumption in sharded clusters.
• The C++ driver now monitors replica set health with the isMaster command instead of replSetGetStatus. This allows the C++ driver to support systems that require authentication.
• New cursor.maxTimeMS() and corresponding maxTimeMS option for commands to specify a time limit.

Tool Improvements

• mongo shell supports a global /etc/mongorc.js.
• All MongoDB executable files now support the --quiet option to suppress all logging output except for error messages.
• mongoimport uses the input filename, without the file extension if any, as the collection name if run without the -c or --collection specification.
• mongoexport can now constrain export data using --skip and --limit, as well as order the documents in an export using the --sort option.
• mongostat can support the use of --rowcount (-n) with the --discover option to produce the specified number of output lines.
• Add strict mode representation for data_numberlong for use by mongoexport and mongoimport.

MongoDB Enterprise Features

The following changes are specific to MongoDB Enterprise Editions:

MongoDB Enterprise for Windows

MongoDB Enterprise for Windows is now available. It includes support for Kerberos, SSL, and SNMP.

MongoDB Enterprise for Windows does not include LDAP support for authentication. However, MongoDB Enterprise for Linux supports using LDAP authentication with an ActiveDirectory server.

MongoDB Enterprise for Windows includes OpenSSL version 1.0.1g.

Auditing

MongoDB Enterprise adds auditing capability for mongod and mongos instances. See Auditing for details.

LDAP Support for Authentication

MongoDB Enterprise provides support for proxy authentication of users. This allows administrators to configure a MongoDB cluster to authenticate users by proxying authentication requests to a specified Lightweight Directory Access Protocol (LDAP) service. See Authenticate Using SASL and LDAP with OpenLDAP and Authenticate Using SASL and LDAP with ActiveDirectory for details.

MongoDB Enterprise for Windows does not include LDAP support for authentication. However, MongoDB Enterprise for Linux supports using LDAP authentication with an ActiveDirectory server.

MongoDB does not support LDAP authentication in mixed sharded cluster deployments that contain both version 2.4 and version 2.6 shards. See Upgrade MongoDB to 2.6 for upgrade instructions.

Expanded SNMP Support

MongoDB Enterprise has greatly expanded its SNMP support to provide SNMP access to nearly the full range of metrics provided by db.serverStatus().

See also

SNMP Changes

Additional Information

Changes Affecting Compatibility

• Compatibility Changes in MongoDB 2.6
  • Index Changes
    • Enforce Index Key Length Limit
    • Index Specifications Validate Field Names
    • ensureIndex and Existing Indexes
  • Write Method Acknowledgements
  • db.collection.aggregate() Change
  • Write Concern Validation
  • Security Changes
    • New Authorization Model
    • SSL Certificate Hostname Validation
  • 2dsphere Index Version 2
  • Log Messages
    • Timestamp Format Change
  • Package Configuration Changes
    • Default bindIp for RPM/DEB Packages
    • SNMP Changes
  • Remove Method Signature Change
  • Update Operator Syntax Validation
  • Updates Enforce Field Name Restrictions
  • Query and Sort Changes
    • Enforce Field Name Restrictions
    • Sparse Index and Incomplete Results
    • sort() Specification Values
    • skip() and _id Queries
    • explain() Retains Query Plan Cache
    • Geospatial Changes
      • $maxDistance Changes
      • Deprecated $uniqueDocs
      • Stronger Validation of Geospatial Queries
    • Query Operator Changes
      • $not Query Behavior Changes
      • null Comparison Queries
      • $all Operator Behavior Change
      • $mod Operator Enforces Strict Syntax
      • $where Must Be Top-Level
      • $exists and notablescan
      • MinKey and MaxKey Queries
      • Nested Array Queries with $elemMatch
    • Text Search Compatibility
  • Replica Set/Sharded Cluster Validation
    • Shard Name Checks on Metadata Refresh
    • Replica Set Vote Configuration Validation
  • Time Format Changes
  • Other Resources

Some changes in 2.6 can affect compatibility and may require user actions. The 2.6 mongo shell provides a db.upgradeCheckAllDBs() method to perform a check for upgrade preparedness for some of these changes.

See Compatibility Changes in MongoDB 2.6 for a detailed list of compatibility changes.

See also

All Backwards incompatible changes (JIRA).

Upgrade Process

• Upgrade MongoDB to 2.6
  • Upgrade Recommendations and Checklists
    • Upgrade Requirements
    • Preparedness
    • Authentication
    • Downgrade Limitations
    • Package Upgrades
  • Upgrade MongoDB Processes
    • Upgrade Standalone mongod Instance to MongoDB 2.6
    • Upgrade a Replica Set to 2.6
      • Upgrade secondary members of the replica set.
      • Step down the replica set primary.
      • Upgrade the primary.
    • Upgrade a Sharded Cluster to 2.6
      • Considerations
      • Upgrade Sharded Clusters
        • Disable the Balancer.
        • Upgrade the cluster’s meta data.
        • Ensure mongos --upgrade process completes successfully.
        • Upgrade the remaining mongos instances to v2.6.
      • Complete Sharded Cluster Upgrade
  • Upgrade Procedure
    • Stop the existing mongod instance.
    • Start the new mongod instance.
• Upgrade User Authorization Data to 2.6 Format
  • Considerations
    • Complete all other Upgrade Requirements
    • Timing
    • Replica Sets
    • Sharded Clusters
  • Requirements
  • Procedure
    • Connect to MongoDB instance.
    • Upgrade authorization schema.
      • Run authSchemaUpgrade command.
      • Sharded cluster authSchemaUpgrade consideration.
  • Result
• Downgrade MongoDB from 2.6
  • Downgrade Recommendations and Checklist
    • Downgrade Path
    • Preparedness
    • Procedures
  • Downgrade 2.6 User Authorization Model
    • Considerations
    • Access Control Prerequisites
      • Connect as user with privileges to manage users and roles.
      • Create a role with required privileges.
      • Create a user with the new role.
      • Authenticate as the new user.
    • Procedure
      • Connect and authenticate to MongoDB instance.
      • Create backup of 2.6 admin.system.users collection.
      • Update the version document for the authSchema.
      • Remove existing documents from the admin.system.users collection.
      • Copy documents from the admin.system.backup_users collection.
      • Update the version document for the authSchema.
    • Result
  • Downgrade Updated Indexes
    • Text Index Version Check
    • 2dsphere Index Version Check
  • Downgrade MongoDB Processes
    • Downgrade 2.6 Standalone mongod Instance
    • Downgrade a 2.6 Replica Set
      • Downgrade each secondary member, one at a time.
        • Replace and restart secondary mongod instances.
        • Allow secondary to recover.
      • Step down the primary.
      • Replace and restart former primary mongod.
    • Downgrade a 2.6 Sharded Cluster
      • Requirements
      • Procedure
  • Downgrade Procedure
    • Stop the existing mongod instance.
    • Start the new mongod instance.

See Upgrade MongoDB to 2.6 for full upgrade instructions.

Download

To download MongoDB 2.6, go to the downloads page.

Other Resources

• All JIRA issues resolved in 2.6.
• All Third Party License Notices.

←   Downgrade MongoDB from 3.0 2.6 Changelog  →

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.