Docs Home → Develop Applications → MongoDB Manual
Release Notes for MongoDB 5.3![](/docs/v5.3/assets/link.svg)
Patch Releases![](/docs/v5.3/assets/link.svg)
5.3.2 - Jun 23, 2022![](/docs/v5.3/assets/link.svg)
Issues fixed:
SERVER-65821 Deadlock during setFCV when there are prepared transactions that have not persisted commit/abort decision
SERVER-65429 Balancer defragmentation policy should be cleared on step down
SERVER-64403 Find queries with SORT_MERGE collation-encode the missing sort attribute
SERVER-63531 commitQuorum incorrectly includes buildIndexes:false nodes and error message incorrectly says that only voting nodes are eligible
SERVER-65270 Multi-planned SBE queries involving large documents do not respect the 'sort' option
5.3.1 - April 6, 2022![](/docs/v5.3/assets/link.svg)
The first release available for MongoDB 5.3 is 5.3.1. All mentions of MongoDB 5.3 features and updates are available in version 5.3.1.
For a list of all changes in 5.3.0, see:
For a list of all changes in 5.3.1, see:
Aggregation![](/docs/v5.3/assets/link.svg)
New Aggregation Stages![](/docs/v5.3/assets/link.svg)
MongoDB 5.3 introduces the following aggregation stages:
Stage | Description |
---|---|
Populates |
New Aggregation Operators![](/docs/v5.3/assets/link.svg)
MongoDB 5.3 introduces the following aggregation operators:
Operator | Description |
---|---|
Fills |
setWindowFields
Stage with Transactions and snapshot
Read Concern![](/docs/v5.3/assets/link.svg)
Starting in MongoDB 5.3, you can use the $setWindowFields
stage with transactions and the
"snapshot"
read concern.
Security![](/docs/v5.3/assets/link.svg)
KMIP Key Activation![](/docs/v5.3/assets/link.svg)
Starting in MongoDB 5.3, security.kmip.activateKeys
activates all
newly created KMIP keys upon creation and then periodically checks that
keys are in an active state.
Polling for Active State Keys![](/docs/v5.3/assets/link.svg)
Starting in MongoDB 5.3, security.kmip.keyStatePollingSeconds
sets
the polling interval in seconds at which mongod
polls the KMIP server
for active keys.
Sharding![](/docs/v5.3/assets/link.svg)
Starting in MongoDB 5.3, you can use the new
chunkDefragmentationThrottlingMS
parameter to limit the
rate of split and merge commands run by the balancer when the
chunks in a sharded collection are
defragmented.
General Improvements![](/docs/v5.3/assets/link.svg)
Time Series Collection Improvements![](/docs/v5.3/assets/link.svg)
Starting in MongoDB 5.3, you can use the $geoNear
pipeline
operator on any field in a time series collection.
Clustered Collections![](/docs/v5.3/assets/link.svg)
Starting in MongoDB 5.3, you can create a collection with a clustered index. Collections created with a clustered index are called clustered collections.
To learn about the benefits compared to a normal collection, see Clustered Collections.
serverStatus
Output Change![](/docs/v5.3/assets/link.svg)
Starting in MongoDB 5.3, serverStatus
includes
connections.loadBalanced
which reports the
number of incoming connections received through a load balancer.
getParameter
can Report When Parameters can be Set![](/docs/v5.3/assets/link.svg)
Starting in MongoDB 5.3, getParameter
can report:
whether a parameter can be set at startup
whether a parameter can be set during runtime
You can use the getParameter
command to report parameter
details by passing { showDetails: true }
. You
can use getParameter
to report details on all parameters by passing
{ showDetails: true, allParameters: true }
.
explain
Output Can Includes Fields for Disk Usage on inputStage
![](/docs/v5.3/assets/link.svg)
Starting in MongoDB 5.3, explain
output can include the
following disk usage metrics for a GROUP
explain.executionStats.executionStages.inputStage
that uses the
slot-based execution query engine:
spilledBytesApprox
, the approximate number of in-memory bytes spilled to disk in the stagespilledRecords
, the number of produced records spilled to disk in the stageusedDisk
, whether the stage wrote to disk
For details, see
explain.executionStats.executionStages.inputStage
.
Specify a Timeout for Step Up and Step Down Operations![](/docs/v5.3/assets/link.svg)
Starting in MongoDB 5.3, the fassertOnLockTimeoutForStepUpDown
parameter allows a server that receives a request to step up or down to
terminate if it is unable to comply within the timeout.
Multiple Arbiters![](/docs/v5.3/assets/link.svg)
Starting in MongoDB 5.3, support for multiple arbiters in a replica set is
disabled by default. To enable support for multiple arbiters, start each
node with the allowMultipleArbiters
parameter.
Report an Issue![](/docs/v5.3/assets/link.svg)
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.