Docs Menu
Docs Home
/
MongoDB Manual

Release Notes for MongoDB 3.6

On this page

  • Patch Releases
  • Security
  • Aggregation
  • Array Update Operator Enhancements
  • 3.6 Compatible Drivers
  • Change Streams
  • Client Sessions
  • Server Sessions
  • JSON Schema
  • Replica Sets
  • Sharded Clusters
  • General Enhancements
  • Changes Affecting Compatibility
  • Upgrade Procedures
  • Download
  • Known Issues in 3.6.3
  • Known Issues in 3.6.2
  • Known Issues in 3.6.1
  • Known Issues in 3.6.0
  • Report an Issue

Patch Releases

3.6.23 - Mar 19, 2021

Issues Fixed:

  • SERVER-40361: Reduce memory footprint of plan cache entries

  • SERVER-46686: Explain does not respect maxTimeMS

  • SERVER-50267: Set output limit for 'rawMongoProgramOutput()'

  • TOOLS-2803: [v3.6] Add --config option for password values

  • All JIRA issues closed in 3.6.23

  • 3.6.23 Changelog

3.6.22 - Feb 8, 2021

Issues Fixed:

3.6.21 - Nov 16, 2020

Issues Fixed:

3.6.20 - Sep 14, 2020

Issues Fixed:

3.6.19 - Jul 23, 2020

Issues Fixed:

3.6.18 - May 1, 2020

Issues fixed:

  • SERVER-46466: Race with findAndModify retryable write and session migration

  • SERVER-45935: [3.6] WT error handler incorrectly prints “An unsupported journal format detected”

  • SERVER-45418: DocumentSourceCursor batching memory accounting does not account for empty documents, leads to unbounded memory use for count-like aggregates

  • SERVER-45363: Issue with mongodb text indexes and weights when using wildcard specifier

  • SERVER-35050: Don’t abort collection clone due to negative document count

  • All JIRA issues closed in 3.6.18

  • 3.6.18 Changelog

Note

Fixed issues include those that resolve the following Common Vulnerabilities and Exposure (CVE):

3.6.17 - Jan 27, 2020

Issues fixed:

3.6.16 - Dec 6, 2019

Issues fixed:

3.6.15 - Nov 6, 2019

Issues fixed:

3.6.14 - Aug 26, 2019

Issues fixed:

Note

Fixed issues include those that resolve the following Common Vulnerabilities and Exposures (CVEs):

3.6.13 - Jun 10, 2019

Issues fixed:

Note

Fixed issues include those that resolve the following Common Vulnerabilities and Exposures (CVEs):

3.6.12 - April 8, 2019

Issues fixed:

3.6.11 - Mar 1, 2019

Issues fixed:

  • SERVER-32146: Log slow oplog entry application

  • SERVER-9043: Link flushRouterConfig on the config server and shards

  • SERVER-37624: Sessions never expire when you change value of localLogicalSessionTimeoutMinutes

  • SERVER-38344: Early release of distributed database locks during initial collection sharding results in migration/split failures

  • SERVER-39166: $graphLookup should force a pipeline to split in sharded cluster

  • All JIRA issues closed in 3.6.11

  • 3.6.11 Changelog

3.6.10 - Jan 22, 2019

Issues fixed:

3.6.9 - Nov 16, 2018

Issues fixed:

3.6.8 - Sep 19, 2018

Issues fixed:

3.6.7 - Aug 25, 2018

Issues fixed:

3.6.6 - Jul 10, 2018

Issues fixed:

3.6.5 - May 29, 2018

Issues fixed:

3.6.4 - Apr 13, 2018

Issues fixed:

3.6.3 - February 23, 2018

Issues fixed:

3.6.2 - January 10, 2018

Issues fixed:

  • SERVER-31267: CollectionCloner fails if collection is dropped between getMore calls.

  • SERVER-31625: The contents of Unknown macro: {USER} needs to be escaped when querying for the groups using LDAP server.

  • SERVER-31684: QueryPlanKilled (operation exceeded time limit) in $changeStream with updateLookup.

  • SERVER-31982: Shard does not call config commit chunk migration command with majority writeConcern nor checks for writeConcern errors..

  • SERVER-32246: PID file permission on v3.6 make it not monitorable using pid file.

  • SERVER-32255: UUIDs may be absent from shard secondary local collections.

  • SERVER-32282: Aggregation text search returns text score even if it wasn't requested when targeting multiple shards in a sharded cluster.

  • SERVER-32396 mongo shell failed to connect with 3.6 connection string SRV

  • SERVER-32430: DocumentSourceSort sorts array documents incorrectly if there is a non-simple collation.

  • SERVER-32529: Requiring replSet for shards breaks Queryable Backup.

  • All JIRA issues closed in 3.6.2

  • 3.6.2 Changelog

3.6.1 - Dec 26, 2017

Issues fixed:

Security

Default Bind to Localhost

MongoDB binaries, mongod and mongos, bind to localhost by default.

MONGODB-CR Deprecation

As of MongoDB 3.6, MONGODB-CR authentication mechanism is deprecated.

Authentication Restrictions

To restrict database user connections to specified IP addresses, added authenticationRestrictions parameter to the following:

Commands
Methods

Additional Security Enhancements

  • Added the opensslCipherConfig parameter to control the OpenSSL ciphers when using TLS/SSL encryption.

  • If authentication is turned on, you can only issue a getMore against cursors you created.

  • Added the convertToCapped action to restore role.

    Tip

    See also:

    Backwards Incompatible Features

Aggregation

The following features are available starting in MongoDB 3.6.

More Expressive $lookup

$lookup adds support for specifying multiple join conditions as well as uncorrelated sub-queries by allowing variable specification and pipeline execution on the joined collection.

For details, see the $lookup syntax for Join Conditions and Uncorrelated Sub-queries.

New Aggregation Stages

MongoDB 3.6 adds the following new aggregation pipeline stages:

Operator
Description
Returns a stream of documents containing information on active and/or dormant operations on a mongod instance. Uses the new aggregation helper db.aggregate().
Lists server sessions in the system.sessions collection in the config database. Uses the new aggregation helper db.aggregate().
Lists server sessions cached in memory by the server.

New Aggregation Operators

Operator
Description
Converts an array of key value pairs to a document.
Converts a document to an array of documents representing key-value pairs.
Combines multiple documents into a single document.
Converts a date/time string to a date object.
Constructs a BSON Date object given the date's constituent parts.
Returns a document containing the constituent parts of a date.

New Aggregation Helper

MongoDB 3.6 adds a helper, db.aggregate(), to perform aggregations that do not rely on an underlying collection, such as those that start with $currentOp or $listLocalSessions.

New Aggregation Variable

REMOVE allows for the conditional exclusion of a field.

New Options

aggregate command and the db.collection.aggregate() method support the following new options:

  • hint option to specify the index to use.

    Note

    The hint does not apply to $lookup and $graphLookup stages.

  • comment option to help trace the operation through the database profiler, currentOp, and logs.

Support for Time Zones

MongoDB 3.6 adds support for time zones to aggregation date operators.

Tip

See also:

Aggregation Compatibility Changes

Array Update Operator Enhancements

arrayFilters

The following commands and methods can accept an arrayFilters parameter to specify which elements to modify in an array field:

Commands
Methods

Multi-Element Array Updates

MongoDB 3.6 adds the following new positional operators for update operations on arrays and nested arrays:

  • The all positional $[] operator updates all elements in an array.

  • The filtered positional $[<identifier>] operator updates all elements in an array that match the arrayFilters criteria.

Negative Array Index Position for push

The $position modifier for the $push update operator can accept a negative array index value to indicate a position starting from the end of the array.

3.6 Compatible Drivers

The following drivers are feature compatible with MongoDB 3.6:

Java 3.6+

Python 3.6+

C 1.9+

Go 1.8+

C# 2.5+

Node 3.0+

Ruby 2.5+

Rust 2.1+

Swift 1.2+

Perl 2.0+

PHPC 1.4+

Scala 2.2+

C++ 3.6.6+

DNS-constructed Seedlist mongodb+srv

In addition to the standard connection format, the 3.6 drivers support a DNS-constructed seedlist. For more information, see DNS Seed List Connection Format.

Change Streams

MongoDB 3.6 supports opening change streams against replica sets and sharded clusters with replica set shards.

Change streams allow applications to access real-time data changes without the complexity and risk of tailing the oplog. Applications can use change streams to subscribe to all data changes on a collection and respond to those changes.

You can open a change stream from any 3.6-series driver using the db.collection.watch() method. See the documentation for your preferred driver for complete instructions on usage.

See Change Streams for more information.

Important

To use change streams, featureCompatibilityVersion must be set to "3.6". For more information, see View FeatureCompatibilityVersion and setFeatureCompatibilityVersion.

Client Sessions

Causal Consistency

To provide causal consistency, MongoDB 3.6 enables causal consistency in client sessions. A causally consistent client session denotes that the associated sequence of read and acknowledged write operations have a causal relationship that is reflected by their ordering. Client applications must ensure that only one thread at a time executes these operations in a client session.

Applications can start a client session and associate operations with a specific session. Applications must ensure that only one thread at a time executes these operations in a client session.

Important

To use client sessions:

Retryable Writes

Important

For retryable writes:

Starting in MongoDB 3.6, certain acknowledged write operations on replica sets and sharded clusters are "retryable" to provide handling of transient network errors or replica set elections.

With retryable writes, MongoDB drivers automatically retries these operations upon encountering network errors or encountering a replica set failover during which time the replica set has no primary. To enable retryable writes for the 3.6 drivers, see retryWrites.

As the retry attempt is made only once, the retryable feature can help address transient network errors but not persistent network errors.

For more information on retryable writes, see Retryable Writes.

mongo Shell Changes

MongoDB 3.6 adds the new command-line option --retryWrites to the mongo shell. The option enables Retryable Writes in the mongo shell.

The following new methods have been added to the Mongo() connection object in the mongo shell:

Server Sessions

MongoDB's server sessions, or logical sessions, are the underlying framework used by client sessions to support Causal Consistency and retryable writes.

Important

Applications use client sessions to interface with server sessions.

Server sessions are available for standalone mongod instances, replica sets, and sharded clusters.

Server Session Commands

Starting in 3.6, MongoDB drivers associate all operations with a server session, with the exception of unacknowledged writes. If the deployment enforces authentication/authorization, server sessions are associated with the authenticated users.

The following commands can be used to list, manage, and kill server sessions throughout MongoDB clusters:

Commands
Descriptions
Expires specified server sessions.
Kills all server sessions.
Kills all server sessions that match the specified pattern.
Kills specified server sessions.
Refreshes idle server sessions.
Starts a new server session.

Parameters

The following new parameters are available for server sessions:

Aggregation Stages

To support server sessions, MongoDB 3.6 adds the following new aggregation pipeline stages:

Operator
Description
Lists the server sessions in the system.sessions collection in the config database.
Lists the server sessions cached in memory by the server. Uses the new aggregation helper db.aggregate().

General

serverStatus returns information on the number of logicalSessionRecordCache.

Command Options

Starting in 3.6, MongoDB drivers associate all operations with a server session, with the exception of unacknowledged writes. The following options are available for all commands to support association with a server session:

Important

The mongo shell and the drivers assign these options to the commands in the session.

Option
Type
Description
lsid
Document
The document that specifies the unique ID of the session associated with the command. If the txnNumber is specified, the lsid is required.
txnNumber
64-bit integer

A strictly increasing non-negative number that uniquely identifies the command in the command's session.

If specified, the command must also include the lsid option.

For the delete, insert, and update commands that take an array of statements, the following option is also available:

Important

Do not manually set stmtIds. MongoDB sets the stmtIds to be strictly increasing non-negative numbers.

Option
Type
Description
stmtIds
Array of 32-bit integers
Array of numbers that uniquely identify their respective write operations within the write command.

JSON Schema

MongoDB 3.6 adds the $jsonSchema operator to support document validation using JSON Schema. For details, see $jsonSchema.

To use $jsonSchema, featureCompatibilityVersion must be set to "3.6".

Tip

See also:

Backwards Incompatible Features

Replica Sets

Sharded Clusters

  • Starting in 3.6, shards must be replica sets. To upgrade your sharded cluster to version 3.6, the shard servers must be running as a replica set.

  • Starting in 3.6, all members of a shard replica set, not just the primary, maintain the metadata regarding chunk metadata. This prevents reads from the secondaries from returning orphaned data when not using "available" read concern.

  • Added ShardingTaskExecutorPoolMaxConnecting parameter for mongos to control the rate at which mongos adds connections to a mongod instance.

  • Added orphanCleanupDelaySecs that determines the minimum delay before a migrated chunk is deleted from the source shard.

  • The config.system.sessions collection in the config database may now be sharded.

General Enhancements

MongoDB Compass Packaging

The MongoDB Server download is packaged with a platform-specific installation script for MongoDB Compass Community Edition. This script installs MongoDB Compass as part of the MongoDB Server installation process.

Collection Identifier

Collections have an immutable unique identifier. The featureCompatibilityVersion must be set to "3.6".

Tip

See also:

Backwards Incompatible Features

New Query Operators

MongoDB 3.6 adds the following new query operators:

  • The new $jsonSchema operator matches documents that validate against the given JSON Schema. To use $jsonSchema, featureCompatibilityVersion must be set to "3.6".

  • The $expr allows the use of aggregation expressions within the query language.

Tip

See also:

Backwards Incompatible Features

Removed Operators

MongoDB 3.6 removes the deprecated $pushAll update operator. For more information, see Remove $pushAll Update Operator.

Indexes

  • An index can cover a query on fields within nested documents.

  • Multikey indexes can cover queries over non-array keys if the index tracks which fields make it multikey.

  • When creating an index, you cannot specify * as the name of the index. See Indexes Named *.

Commands

  • Added the following options to the listDatabases command:

    • nameOnly to return only the database names (which does not require database locks) instead of returning both the database names and size information (which does require database locks).

    • filter to return databases that match the specified match criteria on the outputs.

  • Modified behavior of the validate command and the db.collection.validate() method such that only for full validation does the WiredTiger storage engine force a checkpoint, flush all in-memory data to disk, then verify the on-disk data. See also validate Operation.

  • The <database>.system.profile entry for update and delete contains the entire update/delete document applied to the named collection.

  • dropDatabase waits until all collections drops in the database have propagated to a majority of the replica set members.

  • For commands run on replica sets and sharded clusters, the response documents include the operationTime and $clusterTime. See db.runCommand() and db.adminCommand().

  • Deprecated getPrevError command.

Wire Protocol and Compression

  • MongoDB 3.6 introduces a new wire protocol opcode called OP_MSG. This opcode's message format is extensible and designed to subsume the functionality of other opcodes.

  • MongoDB 3.6 adds support for the zlib compressor for --networkMessageCompressors option (or net.compression.compressors setting if using the configuration file). --networkMessageCompressors option (or net.compression.compressors setting) enables network compression for communication among mongod, mongos, mongo shell, and drivers that support the OP_COMPRESSED message format.

  • mongod and mongos enable network compression by default with snappy as the compressor. For more information on network compression, see net.compression.compressors.

Read Concern

  • New "available" read concern is available. For unsharded collections (including collections in a standalone deployment or a replica set deployment), "local" and "available" read concerns behave identically. For sharded clusters, "available" provides greater tolerance for partitions but may return orphan documents if the shard is undergoing chunk migrations.

    Tip

    See also:

    orphanCleanupDelaySecs

  • Starting in MongoDB 3.6, MongoDB enables support for "majority" read concern by default.

    For MongoDB 3.6.1 - 3.6.x, you can disable read concern "majority" to prevent the storage cache pressure from immobilizing a deployment with a primary-secondary-arbiter (PSA) architecture. Disabling "majority" read concern also disables support for change streams

    For more information, see Disable Read Concern Majority.

FTDC

MongoDB 3.6 adds support for Diagnostics Capture (also known as FTDC) in mongos. [1] In previous versions, the feature is available for mongod only. See Diagnostic Parameters.

Note

FTDC is enabled by default.

[1] MongoDB 3.4.14+ also adds mongos support for FTDC.

Additional Enhancements

MongoDB 3.6 includes the following enhancements:

  • Added support for specifying full Unix domain socket paths with --bind_ip.

  • mongod now offers a --timeZoneInfo option. Use this option to specify the path to your system time zone database. The default configuration file included with Linux and macOS packages sets this to /usr/share/zoneinfo.

  • Date operations now accept consistent date ranges across all supported operating systems. You may safely work with years in the range 0 through 9999.

  • The new honorSystemUmask startup option for mongod causes new files created by MongoDB to have the read/write permissions specified by the umask of the user who runs the mongod process. Only available on Linux and macOS systems.

  • The maxWriteBatchSize limit of a database, which indicates the maximum number of write operations permitted in a write batch, raises from 1,000 to 100,000.

  • The planCacheListPlans database command produces the same output as the PlanCache.getPlansByQuery() shell method. The output from both operations now includes a timestamp for when the plans were generated.

  • The new KeysRotationIntervalSec server parameter specifies the number of seconds for which an HMAC signing key is valid before rotating to the next one.

  • The find command's option oplogReplay now supports the $eq operator.

Changes Affecting Compatibility

Some changes can affect compatibility and may require user actions. For a detailed list of compatibility changes, see Compatibility Changes in MongoDB 3.6.

Upgrade Procedures

Important

Feature Compatibility Version 3.4

To upgrade, the 3.4 instances must have featureCompatibilityVersion set to 3.4. To check the version:

db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )

For specific details on verifying and setting the featureCompatibilityVersion as well as information on other prerequisites/considerations for upgrades, refer to the individual upgrade instructions:

If you need guidance on upgrading to 3.6, MongoDB offers major version upgrade services to help ensure a smooth transition without interruption to your MongoDB application.

Download

To download the MongoDB 3.6, go to the MongoDB Download Center

Tip

See also:

All Third Party License Notices

Known Issues in 3.6.3

  • WT-3724:
    MongoDB 3.6 is not tested on APFS, the new filesystem in macOS 10.13 and may encounter errors.

  • Operations that build in-memory structures are not causally consistent; however, only some operations return errors when associated with causally consistent sessions. See Causal Consistency Limitations.

Known Issues in 3.6.2

  • SERVER-31760:
    $expr does not use indexes for equality match against field, including when used as part of a $lookup aggregation stage with foreign pipeline.
  • WT-3724:
    MongoDB 3.6 is not tested on APFS, the new filesystem in macOS 10.13 and may encounter errors.

  • Operations that build in-memory structures are not causally consistent; however, only some operations return errors when associated with causally consistent sessions. See Causal Consistency Limitations.

Known Issues in 3.6.1

  • SERVER-31760:
    $expr does not use indexes for equality match against field, including when used as part of a $lookup aggregation stage with foreign pipeline.
  • WT-3724:
    MongoDB 3.6 is not tested on APFS, the new filesystem in macOS 10.13 and may encounter errors.

  • Operations that build in-memory structures are not causally consistent; however, only some operations return errors when associated with causally consistent sessions. See Causal Consistency Limitations.

Known Issues in 3.6.0

  • SERVER-31760:
    $expr does not use indexes for equality match against field, including when used as part of a $lookup aggregation stage with foreign pipeline.
  • TOOLS-1827:
    When using a URI with SRV, fetched TXT records will be ignored if no query parameters are specified in the command line URI. To get around this, explicitly specify the TLS/SSL setting used to communicate with the database (either ssl=true or ssl=false) in the URI query string.
  • WT-3724:
    MongoDB 3.6 is not tested on APFS, the new filesystem in macOS 10.13 and may encounter errors.

  • Operations that build in-memory structures are not causally consistent; however, only some operations return errors when associated with causally consistent sessions. See Causal Consistency Limitations.

Tip

See also:

All JIRA issues resolved in 3.6.

Report an Issue

To report an issue, see https://github.com/mongodb/mongo/wiki/Submit-Bug-Reports for instructions on how to file a JIRA ticket for the MongoDB server or one of the related projects.

Next

What is MongoDB?