Release Notes for MongoDB 3.6
On this page
- Minor 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
Minor Releases
3.6.19 - July 23, 2020
Issues Fixed:
- SERVER-46487 The mongos routing for scatter/gather ops can have unbounded latency
- SERVER-45610 Some reads work while system is RECOVERING
- SERVER-47695 Write commands run by threads that can survive rollback can fail operationTime invariant in ServiceEntryPoint
- SERVER-47994 Fix for numerical overflow in GeoHash
- SERVER-47686 Upgrade static OpenSSL to 1.1.1g
- All JIRA issues closed in 3.6.19
- 3.6.19 Changelog
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):
- CVE-2020-7921 (See SERVER-45472 )
3.6.17 - Jan 27, 2020
Issues fixed:
- SERVER-42565 : Aggregations and find commands sort missing fields differently
- SERVER-44733 : Change stream should throw ChangeStreamFatalError if a single shard cannot be targeted for updateLookup
- SERVER-44174 : $push and $addToSet should restrict memory usage
- SERVER-37772 : Platform Support: Add Community & Enterprise RHEL 8 x64
- SERVER-45396 : fix the “me” field in isMaster responses when using splithorizon
- WT-5042 : Reduce configuration parsing overhead from checkpoints
- All JIRA issues closed in 3.6.17
- 3.6.17 Changelog
3.6.16 - Dec 6, 2019
Issues fixed:
- SERVER-38002 : Upgrade Pcre to at least 8.42
- SERVER-35463 : Mark listCommands as pre-auth
- SERVER-44584 : Rewriting updates as modifications incorrectly considers logging state
- All JIRA issues closed in 3.6.16
- 3.6.16 Changelog
3.6.15 - Nov 6, 2019
Issues fixed:
- SERVER-39004 : Introduce a quota mechanism for the overflow file
- SERVER-38994 : Step down on SIGTERM
- SERVER-40355 : rs.config that contains an _id greater than the number of nodes will crash
- SERVER-43074 : Do not use a global variable to encode ‘multikeyPath’ information when writing out catalog documents
- WT-4869 : Stop adding cache pressure when eviction is falling behind
- All JIRA issues closed in 3.6.15
- 3.6.15 Changelog
3.6.14 - Aug 26, 2019
Issues fixed:
- SERVER-36443 : Long-running queries should not cause a build-up of unused ChunkManager objects
- SERVER-38945 : SSL performance regression
- SERVER-40134 : Distinct command against a view can return incorrect results when the distinct path is multikey
- SERVER-42055 : Only acquire a collection IX lock to write the lastVote document
- SERVER-42603 : Recent service file change may cause cyclic dependencies
- SERVER-42089 : Platform Support: Remove Enterprise RHEL 6.7 zSeries
- WT-4803 : Implement file_max configuration for Cache Overflow mechanism
- All JIRA issues closed in 3.6.14
- 3.6.14 Changelog
Note
Fixed issues include those that resolve the following Common Vulnerabilities and Exposures (CVEs):
- CVE-2019-2389 (See SERVER-40563 )
- CVE-2019-2390 (See SERVER-42233 )
3.6.13 - Jun 10, 2019
Issues fixed:
- SERVER-16571 : Use Actual Memory Constraint vs. Total System Memory When They Differ
- SERVER-38984 : Attach IDs to users
- SERVER-41213 : Unique background index builds may produce inconsistent keys
- SERVER-37765 : Platform Support: Remove Ubuntu 14.04
- SERVER-37774 : Platform Support: Remove Enterprise Ubuntu 16.04 PPCLE
- All JIRA issues closed in 3.6.13
- 3.6.13 Changelog
Note
Fixed issues include those that resolve the following Common Vulnerabilities and Exposures (CVEs):
- CVE-2019-2386 (See SERVER-38984 )
3.6.12 - April 8, 2019
Issues fixed:
- SERVER-35219 : Regain MongoDB balancer performance with sessions
- SERVER-39847 : Migrating session info can trigger fassert when destination shard has transaction history truncated by oplog
- SERVER-37255 : replSetReconfig with concurrent election can trigger invariant
- SERVER-39394 : Views collation check should traverse through nested $lookup pipelines
- SERVER-39487 : Aggregation operator $sqrt output for NumberDecimal is the same as $exp
- SERVER-37722 : Quiet mode does not suppress connection end events
- All JIRA issues closed in 3.6.12
- 3.6.12 Changelog
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:
- SERVER-29825 : Do not allow rename from unreplicated to replicated DB or vice-versa
- SERVER-35936 : MongoDB Community installer fails to install Compass
- SERVER-36977 : Initial mongod.log is created using umask vs mode 600
- SERVER-37080 : Implement
tuneable batch size for chunk migrations - SERVER-37616 : Implement
tuneable batch size for the rangedeleter - SERVER-37182 : Different values when referencing whole object vs. a field of that object after $arrayToObject
- SERVER-37200 : $match stage following $listSessions not working against mongos
- All JIRA issues closed in 3.6.10
- 3.6.10 Changelog
3.6.9 - Nov 16, 2018
Issues fixed:
- SERVER-32943 : Query during background index build can lead to suboptimal cached plan
- SERVER-35657 : Do not delay journal flushes when operations are waiting for oplog visibility
- SERVER-37058 : Update with numeric field names inside an array can cause validation to fail
- SERVER-37132 : Negation of $in with regex can incorrectly plan from the cache, leading to missing query results
- All JIRA issues closed in 3.6.9
- 3.6.9 Changelog
3.6.8 - Sep 19, 2018
Issues fixed:
- SERVER-34204 : Tailable cursor fails on getMore against a sharded cluster.
- SERVER-34846 : Covered index with collated field returns incorrect result when collation not involved in match or sort.
- SERVER-37002 : Dropping a collection with long index names via rename fails under MMAPv1.
- SERVER-36149 : Fix privileges on setFCV virtual namespace.
- All JIRA issues closed in 3.6.8
- 3.6.8 Changelog
3.6.7 - Aug 25, 2018
Issues fixed:
- SERVER-27725 : Use batch insert when migrating chunks
- SERVER-36070 : Aggregation with $out results in error when Auditing is enabled
- TOOLS-2075 : mongoreplay always replays to secondary
- All JIRA issues closed in 3.6.7
- 3.6.7 Changelog
3.6.6 - Jul 10, 2018
Issues fixed:
- SERVER-33538 :
mapReduce“replace” on a sharded output collection can lead to UUIDCatalog inconsistencies. - SERVER-32999 : Platform Support: Remove Debian 7 builds.
- SERVER-5461 Add
syncSourceHostfield toreplSetGetStatusoutput.