On this page本页内容
MongoDB 5.3 release candidates are not yet available. MongoDB 5.3的候选版本尚未发布。This version of the manual is for an upcoming release and is currently a work in progress.此版本的手册即将发布，目前正在进行中。
MongoDB 5.3 introduces the following aggregation stages:MongoDB 5.3引入了以下聚合阶段：
| Stage | |
|---|---|
$fill |
|
MongoDB 5.3 introduces the following aggregation operators:MongoDB 5.3引入了以下聚合运算符：
$linearFill |
|
setWindowFields Stage with Transactions and snapshot Read ConcernsetWindowFields阶段配合事务以及snapshot读取关注点Starting in MongoDB 5.3, you can use the 从MongoDB 5.3开始，您可以在事务中使用$setWindowFields stage with transactions and the "snapshot" read concern.$setWindowFields阶段和"snapshot"读取关注。
serverStatusStarting in MongoDB 5.3, 从MongoDB 5.3开始，serverStatus includes connections.loadBalanced which reports the number of incoming connections received through a load balancer.serverStatus包括connections.loadBalanced，它报告通过负载均衡器接收的传入连接数。
getParameterStarting in MongoDB 5.3, 从MongoDB 5.3开始，getParameter can report:getParameter可以报告：
You can use the 可以使用getParameter command to report parameter details by passing { showDetails: true }. getParameter命令通过传递{showDetails:true}来报告参数详细信息。You can use 通过传递getParameter to report details on all parameters by passing { showDetails: true, allParameters: true }.{ showDetails: true, allParameters: true }，可以使用getParameter报告所有参数的详细信息。
Starting in MongoDB 5.3, the 从MongoDB 5.3开始，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.fassertOnLockTimeoutForStepUpDown参数允许接收请求的服务器在超时时间内无法遵守时终止。
Starting in MongoDB 5.3 Enterprise, you can use an external Key Management Interoperability Protocol (KMIP) server to securely manage the keys for encrypting the MongoDB audit log.从MongoDB 5.3 Enterprise开始，您可以使用外部密钥管理互操作性协议（KMIP）服务器来安全地管理加密MongoDB审核日志的密钥。
Starting in MongoDB 5.3, 从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.security.kmip.activateKeys在创建时激活所有新创建的KMIP密钥，然后定期检查密钥是否处于活动状态。
Starting in MongoDB 5.3, 从MongoDB 5.3开始，security.kmip.keyStatePollingSeconds sets the polling interval in seconds at which mongod polls the KMIP server for active keys.security.kmip.keyStatePollingSeconds s设置mongod轮询KMIP服务器的活动密钥的轮询间隔（以秒为单位）。
Starting in MongoDB 5.3, you can use the new 从MongoDB 5.3开始，可以使用新的chunkDefragmentationThrottlingMS parameter to limit the rate of split and merge commands run by the balancer when the chunks in a sharded collection are defragmented.chunkDefragmentationThrottlingMS参数来限制分片化集合中的块进行碎片整理时均衡器运行的拆分和合并命令的速率。
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.要报告问题，请参阅https://github.com/mongodb/mongo/wiki/Submit-Bug-Reports了解有关如何为MongoDB服务器或其中一个相关项目提交JIRA票证的说明。