shutdown (database command数据库命令)

Specify 1.指定1。

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的任何正在进行的操作，并可能导致意外行为。

You can pause and resume in-progress index builds using force. See shutdown on Replica Set Members for more information.您可以使用force暂停和恢复正在进行的索引构建。有关详细信息，请参阅副本集成员上的shutdown。

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收到关闭请求，则主服务器：

1. Attempts to step down to a secondary.试图降级到secondary。

   If the step down fails and a:如果降级失败，并且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字段为真或
   • SIGTERM signal was sent to mongod, mongod always continues the shut down steps.SIGTERM信号被发送给mongod，mongod总是继续关闭步骤。
2. Enters the quiesce period.进入停顿期。
3. Ends any remaining database operations.结束所有剩余的数据库操作。
4. Shuts down.关闭。

For a mongod secondary or mongos shut down request, the quiesce period is entered after a shut down was requested.对于mongodsecondary或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, orshutdownTimeoutMillisForSignaledShutdown如果向mongod发送了SIGTERM信号，则关闭服务器参数，或
• 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. New operations are sent to other replica set nodes.如果当前节点在从主节点降级后处于SECONDARY状态，则timeoutSecs中指定的任何剩余时间都将用于停顿期，这允许完成现有操作。新操作被发送到其他副本集节点。

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. 新的操作被发送到其他mongos节点。In MongoDB versions earlier than 5.0, mongos shuts down immediately and does not use timeoutSecs.在早于5.0的MongoDB版本中，mongos会立即关闭并且不使用timeoutSecs。

Optional. 可选。A user-provided comment to attach to this command. Once set, this comment appears alongside records of this command in the following locations:用户提供了要附加到此命令的注释。设置后，此注释将与此命令的记录一起出现在以下位置：

• mongod log messages日志消息, in the attr.command.cursor.comment field.，在attr.command.cursor.comment字段中。
• Database profiler数据库分析器 output, in the command.comment field.输出，在command.comment字段中。
• currentOp output, in the command.comment field.输出，在command.comment字段中。

A comment can be any valid BSON type (string, integer, object, array, etc).注释可以是任何有效的BSON类型（字符串、整数、对象、数组等）。