db.shutdownServer()

db.shutdownServer()

Shuts down the current mongod or mongos process cleanly and safely. 干净安全地关闭当前mongod或mongos进程。You must issue the db.shutdownServer() operation against the admin database.您必须对管理数据库发出db.shutdownServer()操作。

db.shutdownServer() has this syntax:具有以下语法：

db.shutdownServer({
  force: <boolean>,
  timeoutSecs: <int>
})

The method takes these fields:该方法采用以下字段：

Field字段	Description描述
force	Optional.可选的。Specify true to force the mongod or mongos to shut down. 指定true以强制关闭mongod或mongos。Force shutdown interrupts any ongoing operations on the mongod or mongos and may result in unexpected behavior. 强制关闭会中断mongod或mongos上正在进行的任何操作，并可能导致意外行为。
timeoutSecs	Optional.可选的。Starting in MongoDB 5.0, mongod and mongos enter a quiesce period to allow any ongoing database operations to complete before shutting down.从MongoDB 5.0开始，mongod和mongos进入一个停顿期，允许在关闭之前完成任何正在进行的数据库操作。 If a mongod primary receives a shut down request, the primary: 如果mongodprimary收到关闭请求，则primary： Attempts to step down to a secondary.尝试降级到secondary。 If the step down fails and a: 如果降压失败，并且出现： shutdown or db.shutdownServer() command was run, mongod only continues the shut down steps if the force field is true, or ashutdown或db.shutdownServer()命令运行时，mongod仅在force字段为true，或 SIGTERM signal was sent to mongod, mongod always continues the shut down steps.信号被发送到mongod，mongod总是继续关闭步骤。 Enters the quiesce period.进入静止期。 Ends any remaining database operations.结束所有剩余的数据库操作。 Shuts down.关闭。 For a mongod secondary or mongos shut down request, the quiesce period is entered after a shut down was requested.对于mongod secondary或mongos关闭请求，在请求关闭后输入静止期。 The quiesce period is specified by the: 静止期由以下内容指定： timeoutSecs field if a shutdown or db.shutdownServer() command was run, ortimeoutSecs字段（如果运行了shutdown或db.shutdownServer()命令），或者 shutdownTimeoutMillisForSignaledShutdown server parameter if a SIGTERM signal was sent to mongod, or服务器参数，如果SIGTERM信号被发送到mongod，或者 mongosShutdownTimeoutMillisForSignaledShutdown server parameter if a SIGTERM signal was sent to mongos.mongosShutdownTimeoutMillisForSignaledShutdown服务器参数（如果向mongos发送了SIGTERM信号）。 Clients cannot open new connections to a mongod or mongos that is shutting down.客户端无法打开与正在关闭的mongod或mongos的新连接。 timeoutSecs specifies a time period in seconds. The default is: 指定以秒为单位的时间段。默认值为： 15 seconds starting in MongoDB 5.0.在MongoDB 5.0中启动15秒。 10 seconds in MongoDB versions earlier than 5.0.在5.0之前的MongoDB版本中为10秒。 mongod uses timeoutSecs as follows: 使用timeoutSecs，如下所示： If the current node is the primary node of a replica set, mongod waits for a period of up to the number of seconds specified by the timeoutSecs field for an electable node to catch up before stepping down the primary node. 如果当前节点是副本集的primary节点，mongod将等待timeoutSecs字段指定的秒数，以便可选择节点在退出主节点之前赶上。For details about the catch up time, see replication lag.有关追赶时间的详细信息，请参阅复制滞后。 If the current node is in the SECONDARY state after stepping down from being the primary, any remaining time specified in timeoutSecs is used for a quiesce period, which allows existing operations to complete. 如果当前节点在从主节点退出后处于SECONDARY状态，则timeoutSecs中指定的任何剩余时间都将用于静止期，从而允许完成现有操作。New operations are sent to other replica set nodes.新操作将发送到其他副本集节点。 Starting in MongoDB 5.0, mongos uses timeoutSecs as a quiesce period, which allows existing operations to complete. 从MongoDB 5.0开始，mongos使用timeoutSecs作为一个静止期，允许现有操作完成。New operations are sent to other mongos nodes. In MongoDB versions earlier than 5.0, mongos shuts down immediately and does not use timeoutSecs.新操作被发送到其他mongos节点。在MongoDB 5.0之前的版本中，mongos会立即关闭并且不使用timeoutSecs。 For a mongod primary in MongoDB 4.4 and earlier, timeoutSecs specifies the time in seconds that the primary waits for a secondary to catch up for the shutdownServer command. 对于MongoDB 4.4及更早版本中的mongod-primary，timeoutSecs指定primary等待secondary赶上shutdownServer命令的时间（以秒为单位）。If no secondaries catch up within timeoutSecs, the shutdownServer command fails. 如果在timeoutSecs内没有任何辅助设备赶上，则shutdownServer命令将失败。

This operation provides a wrapper around the shutdown command.此操作提供了shutdown命令的包装。

db.getSiblingDB("admin").shutdownServer()

db.getSiblingDB("admin").shutdownServer({ "force" : true })

db.getSiblingDB("admin").shutdownServer({ "timeoutSecs": 60 })