$currentOp (aggregation)

~~On this page~~本页内容

~~Definition~~定义
~~Constraints~~限制
~~Examples~~实例
~~Output Fields~~输出字段

Definition定义

$currentOp

~~Returns a stream of documents containing information on active and/or dormant operations as well as inactive sessions that are holding locks as part of a transaction.~~ 返回一个文档流，其中包含有关活动和/或休眠操作以及作为事务一部分持有锁的非活动会话的信息。~~The stage returns a document for each operation or session.~~ 该阶段为每个操作或会话返回一个文档。~~To run $currentOp, use the db.aggregate() helper on the admin database.~~要运行$currentOp，请在admin数据库上使用db.aggregate()助手。

~~The $currentOp aggregation stage is preferred over the currentOp command and its mongosh helper method db.currentOp().~~ currentOp聚合阶段比currentOp命令及其mongosh辅助方法db.currentOp()更可取。Because the currentOp command and db.currentOp() helper method return the results in a single document, the total size of the currentOp result set is subject to the maximum 16MB BSON size limit for documents. 由于currentOp命令和db.currentOp()辅助方法在单个文档中返回结果，因此currentOp结果集的总大小受文档的最大16MB BSON大小限制。~~The $currentOp stage returns a cursor over a stream of documents, each of which reports a single operation.~~ $currentOp阶段在文档流上返回一个游标，每个文档流报告一个操作。~~Each operation document is subject to the 16MB BSON limit, but unlike the currentOp command, there is no limit on the overall size of the result set.~~每个操作文档都受16MB BSON限制，但与currentOp命令不同，结果集的总体大小没有限制。

$currentOp ~~also enables you to perform arbitrary transformations of the results as the documents pass through the pipeline.~~还使您能够在文档通过管道时对结果执行任意转换。

Syntax语法

{ $currentOp: { allUsers: <boolean>, idleConnections: <boolean>, idleCursors: <boolean>, idleSessions: <boolean>, localOps: <boolean> } }

$currentOp ~~takes an options document as its operand:~~将选项文档作为其操作数：

~~Option~~选项	~~Description~~描述
`allUsers`	~~Boolean.~~布尔值。 ~~If set to `false`, `$currentOp` only reports on operations/idle connections/idle cursors/idle sessions belonging to the user who ran the command.~~如果设置为`false`，`$currentOp`只报告属于运行该命令的用户的操作/空闲连接/空闲游标/空闲会话。 ~~If set to `true`, `$currentOp` reports operations belonging to all users.~~如果设置为`true`，`$currentOp`将报告属于所有用户的操作。 Note ~~For standalone and replica sets that enforce access control, `inprog` privilege is required if `allUsers: true`.~~对于强制访问控制的独立集和副本集，如果`allUsers:true`，则需要`inprog`权限。 ~~For sharded clusters that enforce access control, the `inprog` privilege is required to run `$currentOp`.~~ 对于强制访问控制的分片集群，运行`$currentOp`需要`inprog`权限。 ~~Defaults to `false`.~~ 默认为`false`。
`idleConnections`	~~Boolean.~~布尔值。~~If set to `false`, `$currentOp` only reports active operations.~~ 如果设置为`false`，则`$currentOp`仅报告活动操作。~~If set to `true`, `$currentOp` returns all operations, including idle connections.~~如果设置为`true`，`$currentOp`将返回所有操作，包括空闲连接。 ~~Defaults to `false`.~~ 默认为`false`。
`idleCursors`	~~Boolean.~~布尔值。 ~~If set to `true`, `$currentOp` reports on cursors that are "idle"; i.e. open but not currently active in a `getMore` operation.~~如果设置为`true`，`$currentOp`将报告“空闲”的游标；即在`getMore`操作中打开但当前未处于活动状态。 ~~Information on idle cursors have the `type` set to `"idleCursor"`.~~有关空闲游标的信息的`type`设置为`"idleCursor"`。 ~~Information on cursors currently active in a `getMore` operation information have the `type` set to `"op"` and `op` set to `getmore`.~~`getMore`操作信息中当前活动的游标信息的`type`设置为`"op"`，`op`设置为`getMore`。 ~~Defaults to `false`.~~ 默认为`false`。
`idleSessions`	~~Boolean.~~布尔值。 ~~If set to `true`, in addition to active/dormant operations, `$currentOp` reports on:~~如果设置为`true`，除了活动/休眠操作外，`$currentOp`还会报告： ~~Inactive sessions that are holding locks as part of a transaction. Each inactive session appears as a separate document in the `$currentOp` stream.~~作为事务的一部分持有锁的非活动会话。每个非活动会话在`$currentOp`流中显示为一个单独的文档。 ~~The document for a session includes information on the session ID in the `lsid` field and the transaction in the `transaction` field.~~会话的文档包括`lsid`字段中的会话ID信息和`transaction`字段中的事务信息。 ~~Information on idle sessions have the `type` set to `"idleSession"`.~~有关空闲会话的信息的`type`设置为`"idleSession"`。 `$currentOp.twoPhaseCommitCoordinator` in `inactive` `state` ~~If set to `false`, `$currentOp` doesn't report on:~~如果设置为`false`，`$currentOp`不会报告： ~~Inactive sessions~~非活动会话 ~~`$currentOp.twoPhaseCommitCoordinator` information in `inactive` `state`~~`$currentOp.twoPhaseCommitCoordinator`信息处于`inactive`状态 ~~Defaults to `true`.~~ 默认为`true`。
`localOps`	~~Boolean.~~布尔值。~~If set to `true` for an aggregation running on `mongos`, `$currentOp` reports only operations running locally on that `mongos`.~~ 如果在`mongos`上运行的聚合设置为`true`，则`$currentOp`仅报告在该`mongos`本地运行的操作。~~If `false`, then `$currentOp` instead reports operations running on the shards.~~如果为`false`，那么`$currentOp`将报告在分片上运行的操作。 ~~The `localOps` parameter has no effect for `$currentOp` aggregations running on `mongod`.~~`localOps`参数对`mongod`上运行的`$currentOp`聚合没有影响。 ~~Defaults to `false`.~~ 默认为`false`。
`backtrace`	~~Boolean.~~布尔值。~~Determines whether callstack information is returned as part of the `waitingForLatch` output field.~~ 确定是否将调用堆栈信息作为`waitingForLatch`输出字段的一部分返回。 ~~If set to `true`, `$currentOp` includes `waitingForLatch.backtrace` field that contains the callstack information, if available. If unavailable, the field contains an empty array.~~如果设置为`true`，`$currentOp`包括`waitingForLatch.backtrace`字段，该字段包含调用堆栈信息（如果可用）。如果不可用，则该字段包含一个空数组。 ~~If set to `false`, `$currentOp` omits the `waitingForLatch.backtrace` field.~~如果设置为`false`，`$currentOp`将省略`waitingForLatch.backtrace`字段。 ~~Defaults to `false`.~~ 默认为`false`。

~~Omitting any of the above parameters causes $currentOp to use that parameter's default value. Specify an empty document, as shown below, to use the default values of all parameters.~~省略上述任何参数都会导致$currentOp使用该参数的默认值。指定一个空文档，如下所示，以使用所有参数的默认值。

{ $currentOp: { } }

Constraints限制

Pipeline管道

$currentOp ~~must be the first stage in the pipeline.~~必须是管道中的第一阶段。
~~Pipelines that start with $currentOp can only be run on the admin database.~~以$currentOp开头的管道只能在admin数据库上运行。

Access Control访问控制

~~For standalone and replica sets that enforce access control, inprog privilege is required to run $currentOp if allUsers: true.~~对于强制访问控制的独立集和副本集，如果allUsers:true，则需要inprog权限才能运行$currentOp。
~~For sharded clusters that enforce access control, the inprog privilege is required to run $currentOp.~~对于强制访问控制的分片集群，运行$currentOp需要inprog权限。

Transactions事务

~~$currentOp is not allowed in transactions.~~在事务中不允许$currentOp。

Redaction编辑

~~When using Queryable Encryption, $currentOp output redacts certain information:~~使用可查询加密时，$currentOp输出会编辑某些信息：

~~The output omits all fields after "command".~~输出省略了"command"之后的所有字段。
~~The output redacts "command" to include only the first element, $comment, and $db.~~输出对“命令”进行编辑，使其仅包括第一个元素$comment和$db。

Examples实例

~~The following examples show how to use the $currentOp aggregation stage.~~以下示例显示了如何使用$currentOp聚合阶段。

Inactive Sessions非活动会话

~~This example returns information on inactive sessions that are holding locks as part of a transaction. Specifically:~~此示例返回作为事务一部分持有锁的非活动会话的信息。具体而言：

~~The first stage returns documents for all active operations as well as inactive sessions that are holding locks as part of a transaction.~~第一阶段返回所有活动操作以及作为事务一部分持有锁的非活动会话的文档。
~~The second stage filters for documents related to inactive sessions that are holding locks as part of a transaction.~~第二阶段筛选与作为事务一部分持有锁的非活动会话相关的文档。

db.getSiblingDB("admin").aggregate( [
   { $currentOp : { allUsers: true, idleSessions: true } },
   { $match : { active: false, transaction : { $exists: true } } }
] )

~~You can use $currentOp.type to specify an equivalent filter:~~您可以使用$currentOp.type指定等效的筛选器：

db.getSiblingDB("admin").aggregate( [
   { $currentOp : { allUsers: true, idleSessions: true } },
   { $match : { type: "idleSession" } }
] )

Tip

~~For transactions on a sharded cluster, starting in version 4.2.1, include localOps:true in the aforementioned examples for a composite view of the transactions.~~对于分片集群上的事务，从4.2.1版本开始，在前面提到的事务复合视图示例中包括localOps:true。

~~Both operations return documents of the form:~~两个操作都返回表单的文档：

~~Replica Set~~复制副本集 ~~Sharded Cluster (localOps: true)~~分片集群(localOps:true）~~Sharded Cluster~~分片集群

~~When run on a mongod that is part of a replica set:~~当在作为复制集一部分的mongod上运行时：

{
   "type" : "idleSession",
   "host" : "example.mongodb.com:27017",
   "desc" : "inactive transaction",
   "client" : "198.51.100.1:50428",
   "connectionId" : NumberLong(32),
   "appName" : "",
   "clientMetadata" : {
      "driver" : {
         "name" : "PyMongo",
         "version" : "3.9.0"
      },
      "os" : {
         "type" : "Darwin",
         "name" : "Darwin",
         "architecture" : "x86_64",
         "version" : "10.14.5"
      },
      "platform" : "CPython 3.7.1.final.0"
   },
   "lsid" : {
      "id" : UUID("ff21e1a9-a130-4fe0-942f-9e6b6c67ea3c"),
      "uid" : BinData(0,"3pxqkATNUYKV/soT7qqKE0zC0BFb0pBz1pk4xXcSHsI=")
   },
   "transaction" : {
      "parameters" : {
         "txnNumber" : NumberLong(4),
         "autocommit" : false,
         "readConcern" : {
            "level" : "snapshot",
            "afterClusterTime" : Timestamp(1563892246, 1)
         }
      },
      "readTimestamp" : Timestamp(0, 0),
      "startWallClockTime" : "2019-07-23T10:30:49.461-04:00",
      "timeOpenMicros" : NumberLong(1913590),
      "timeActiveMicros" : NumberLong(55),
      "timeInactiveMicros" : NumberLong(1913535),
      "expiryTime" : "2019-07-23T10:31:49.461-04:00"
   },
   "waitingForLock" : false,
   "active" : false,
   "locks" : {
      "ReplicationStateTransition" : "w",
      "Global" : "w",
      "Database" : "w",
      "Collection" : "w"
   },
   "lockStats" : {
      "ReplicationStateTransition" : {
         "acquireCount" : {
            "w" : NumberLong(5)
         }
      },
      "Global" : {
         "acquireCount" : {
            "r" : NumberLong(3),
            "w" : NumberLong(1)
         }
      },
      "Database" : {
         "acquireCount" : {
            "r" : NumberLong(2),
            "w" : NumberLong(1)
         }
      },
      "Collection" : {
         "acquireCount" : {
            "w" : NumberLong(1)
         }
      },
      "Mutex" : {
         "acquireCount" : {
            "r" : NumberLong(3)
         }
      },
      "oplog" : {
         "acquireCount" : {
            "r" : NumberLong(2)
         }
      }
   },
   "waitingForFlowControl" : false,
   "flowControlStats" : {},
}

~~Starting in version 4.2.1, $currentOp run with localOps:true provides a composite view (rather than per shard information) of the in-progress transactions run on that mongos.~~从4.2.1版本开始，使用localOps:true运行的$currentOp提供了在mongos上运行的正在进行的事务的合成视图（而不是每个分片的信息）。

db.getSiblingDB("admin").aggregate( [
   { $currentOp : { allUsers: true, idleSessions: true, localOps: true } },
   { $match : { type: "idleSession" } }
] );

// or

db.getSiblingDB("admin").aggregate( [
   { $currentOp : { allUsers: true, idleSessions: true, localOps: true } },
   { $match : { active: false, transaction : { $exists: true } } }
] )

{
   "type" : "idleSession",
   "host" : "example.mongodb.com:27017",
   "desc" : "inactive transaction",
   "client" : "198.51.100.1:49618",
   "connectionId" : NumberLong(48),
   "appName" : "",
   "clientMetadata" : {
      "driver" : {
         "name" : "PyMongo",
         "version" : "3.9.0"
      },
      "os" : {
         "type" : "Darwin",
         "name" : "Darwin",
         "architecture" : "x86_64",
         "version" : "10.14.6"
      },
      "platform" : "CPython 3.7.1.final.0",
      "mongos" : {
         "host" : "example.mongodb.com:27017",
         "client" : "198.51.100.1:53268",
         "version" : "4.2.1"
      }
   },
   "lsid" : {
      "id" : UUID("2c9ce111-133e-45b7-a00f-a7871005cae1"),
      "uid" : BinData(0,"3pxqkATNUYKV/soT7qqKE0zC0BFb0pBz1pk4xXcSHsI=")
   },
   "active" : false,
   "transaction" : {
      "parameters" : {
         "txnNumber" : NumberLong(2),
         "autocommit" : false,
         "readConcern" : {
            "level" : "snapshot",
            "afterClusterTime" : Timestamp(1571869019, 2)
         }
      },
      "globalReadTimestamp" : Timestamp(1571869019, 2),
      "startWallClockTime" : "2019-10-23T18:16:59.341-04:00",
      "timeOpenMicros" : NumberLong(169244639),
      "timeActiveMicros" : NumberLong(535),
      "timeInactiveMicros" : NumberLong(169244104),
      "numParticipants" : 2,
      "participants" : [
         {
            "name" : "shardB",
            "coordinator" : true,
            "readOnly" : false
         },
         {
            "name" : "shardA",
            "coordinator" : false,
            "readOnly" : false
         }
      ],
      "numReadOnlyParticipants" : 0,
      "numNonReadOnlyParticipants" : 2
   }
}

~~In 4.2.0, you can only return in-progress transactions information when run without localOps:true on the mongos.~~ 在4.2.0中，只有在mongos上没有localOps:true的情况下运行时，才能返回正在进行的事务信息。~~When run without localOps:true on the mongos, the transaction information is per shard.~~当在mongos上不使用localOps:true运行时，事务信息是按分片的。

~~When run on a mongos without localOps:true, the transaction information is per shard.~~当在没有localOps:true的mongos上运行时，事务信息是按分片的。

{
   "shard" : "shardB",
   "type" : "idleSession",
   "host" : "shardB.mongodb.com:27018",
   "desc" : "inactive transaction",
   "client_s" : "198.51.100.1:53961",
   "connectionId" : NumberLong(63),
   "appName" : "",
   "clientMetadata" : {
      "driver" : {
         "name" : "PyMongo",
         "version" : "3.9.0"
      },
      "os" : {
         "type" : "Darwin",
         "name" : "Darwin",
         "architecture" : "x86_64",
         "version" : "10.14.6"
      },
      "platform" : "CPython 3.7.1.final.0",
      "mongos" : {
         "host" : "example.mongodb.com:27017",
         "client" : "198.51.100.1:53976",
         "version" : "4.2.0"
      }
   },
   "lsid" : {
      "id" : UUID("720d403c-8daf-40bb-b61e-329e20b0493b"),
      "uid" : BinData(0,"3pxqkATNUYKV/soT7qqKE0zC0BFb0pBz1pk4xXcSHsI=")
   },
   "transaction" : {
      "parameters" : {
         "txnNumber" : NumberLong(1),
         "autocommit" : false,
         "readConcern" : {
            "level" : "snapshot"
         }
      },
      "readTimestamp" : Timestamp(0, 0),
      "startWallClockTime" : "2019-10-21T18:31:12.192-04:00",
      "timeOpenMicros" : NumberLong(24137008),
      "timeActiveMicros" : NumberLong(52),
      "timeInactiveMicros" : NumberLong(24136956),
      "expiryTime" : "2019-10-21T18:32:12.192-04:00"
   },
   "waitingForLock" : false,
   "active" : false,
   "locks" : {
      "ReplicationStateTransition" : "w",
      "Global" : "w",
      "Database" : "w",
      "Collection" : "w"
   },
   "lockStats" : {
      "ReplicationStateTransition" : {
         "acquireCount" : {
            "w" : NumberLong(3)
         }
      },
      "Global" : {
         "acquireCount" : {
            "r" : NumberLong(1),
            "w" : NumberLong(1)
         }
      },
      "Database" : {
         "acquireCount" : {
            "r" : NumberLong(1),
            "w" : NumberLong(1)
         }
      },
      "Collection" : {
         "acquireCount" : {
            "r" : NumberLong(1),
            "w" : NumberLong(1)
         }
      },
      "Mutex" : {
         "acquireCount" : {
            "r" : NumberLong(6)
         }
      }
   }
}
{
   "shard" : "shardA",
   "type" : "idleSession",
   ...
}

Sampled Queries采样查询

~~This example returns information on query sampling progess.~~此示例返回有关查询采样进程的信息。

~~The first stage returns documents for all active operations.~~第一阶段返回所有活动操作的文档。
~~The second stage filters for documents related to the query analyzer.~~第二阶段筛选与查询分析器相关的文档。

db.getSiblingDB("admin").aggregate( [
   { $currentOp: { allUsers: true, localOps: true } },
   { $match: { desc: "query analyzer" } }
] )

~~This pipeline returns output similar to the following:~~此管道返回类似于以下内容的输出：

~~Replica Set~~复制副本集 ~~Sharded Cluster~~分片集群: mongos ~~Sharded Cluster~~分片集群: mongod --shardsvr

~~When run on a mongod that is part of a replica set:~~当在作为复制集一部分的mongod上运行时：

{
   "desc" : "query analyzer",
   "ns" : "testDb.testColl",
   "collUuid" : UUID("ed9dfb1d-5b7c-4c6b-82e9-b0f537335795"),
   "samplesPerSecond" : 5,
   "startTime" : ISODate("2023-08-08T16:23:22.846Z"),
   "sampledReadsCount" : NumberLong(2),
   "sampledReadsBytes" : NumberLong(346),
   "sampledWritesCount" : NumberLong(3),
   "sampledWritesBytes" : NumberLong(904)
}

~~When run on a mongos that is part of a sharded cluster:~~当在属于分片集群的mongos上运行时：

{
   "desc" : "query analyzer",
   "ns" : "testDb.testColl",
   "collUuid" : UUID("5130b4df-5966-434f-85f0-f8956b5ca74e"),
   "samplesPerSecond" : 5,
   "startTime" : ISODate("2023-08-08T16:15:07.427Z"),
   "sampledReadsCount" : NumberLong(2),
   "sampledWritesCount" : NumberLong(3)
}

~~When run on a mongod --shardsvr that is part of a sharded cluster:~~当在属于分片集群的mongod -shardsvr上运行时：

{
   "desc" : "query analyzer",
   "ns" : "testDb.testColl",
   "collUuid" : UUID("5130b4df-5966-434f-85f0-f8956b5ca74e"),
   "startTime" : ISODate("2023-08-08T16:15:07.427Z"),
   "sampledReadsCount" : NumberLong(2),
   "sampledReadsBytes" : NumberLong(346),
   "sampledWritesCount" : NumberLong(3),
   "sampledWritesBytes" : NumberLong(904)
}

Output Fields输出字段

~~Each output document may contain a subset of the following fields, as relevant for the operation:~~每个输出文档可能包含与操作相关的以下字段的子集：

$currentOp.type

~~The type of operation. Values are either:~~操作的类型。值为：

op
idleSession
idleCursor

~~If the $currentOp.type is op, $currentOp.op provides details on the specific operation.~~如果$currentOp.type是op，则$currentOp.op会提供有关特定操作的详细信息。

$currentOp.host: ~~The name of the host against which the operation is run.~~运行操作所针对的主机的名称。

$currentOp.shard

~~The name of the shard where the operation is running.~~运行操作的分片的名称。

~~Only present for sharded clusters.~~仅适用于分片群集。

$currentOp.desc: ~~A description of the operation.~~操作说明。

$currentOp.connectionId: ~~An identifier for the connection where the specific operation originated.~~发起特定操作的连接的标识符。

$currentOp.client

~~The IP address (or hostname) and the ephemeral port of the client connection where the operation originates.~~发起操作的客户端连接的IP地址（或主机名）和临时端口。

~~For multi-document transactions, $currentOp.client stores information about the most recent client to run an operation inside the transaction.~~对于多文档事务，$currentOp.client存储有关在事务中运行操作的最新客户端的信息。

~~For standalones and replica sets only~~仅适用于单机版和复制集

$currentOp.client_s

~~The IP address (or hostname) and the ephemeral port of the mongos where the operation originates.~~发起操作的mongos的IP地址（或主机名）和临时端口。

~~For sharded clusters only~~仅适用于分片群集

$currentOp.clientMetadata

~~Additional information on the client.~~有关客户端的其他信息。

$currentOp.appName: ~~The identifier of the client application which ran the operation.~~ 运行该操作的客户端应用程序的标识符。~~Use the appName connection string option to set a custom value for the appName field.~~使用appName连接字符串选项为appName字段设置自定义值。

$currentOp.active: ~~A boolean value specifying whether the operation has started.~~ 指定操作是否已启动的布尔值。~~Value is true if the operation has started or false if the operation is idle, such as an idle connection, an inactive session, or an internal thread that is currently idle.~~ 如果操作已启动，则值为true；如果操作处于空闲状态（例如空闲连接、非活动会话或当前空闲的内部线程），则为false。~~An operation can be active even if the operation has yielded to another operation.~~即使某个操作已让位给另一个操作，该操作也可以处于活动状态。

$currentOp.twoPhaseCommitCoordinator

~~Information on either:~~以下信息之一：

~~The commit coordination metrics for a transaction whose write operations span multiple shards.~~写入操作跨越多个分片的事务的提交协调度量。

Commit coordination is handled by a shard, and $currentOp (run either on a mongos or a shard member) returns a shard's coordination information only for transactions the shard is currently coordinating.提交协调由分片处理，$currentOp（在mongos或分片成员上运行）仅为分片当前正在协调的事务返回分片的协调信息。

~~To filter for only the commit coordination metrics:~~要仅筛选提交协调度量，请执行以下操作：
```
db.getSiblingDB("admin").aggregate( [
    { $currentOp: { allUsers: true, idleSessions: true } },
    { $match: { desc: "transaction coordinator" } }
] )
```
~~A specific commit coordination operation (i.e. type is op and desc is "TransactionCoordinator") spawned by the transaction coordinator.~~事务协调器派生的特定提交协调操作（即type为op，desc为"TransactionCoordinator"）。

Note

~~If run with idleSessions: false, $currentOp does not return the $currentOp.twoPhaseCommitCoordinator information in inactive state~~如果使用idleSessions: false运行，则$currentOp不会返回处于inactive状态的$currentOp.twoPhaseCommitCoordinator信息
~~If access control is enabled and allUsers: false, $currentOp does not return $currentOp.twoPhaseCommitCoordinator information.~~如果启用了访问控制并且allUsers: false，则$currentOp不会返回$currentOp.twoPhaseCommitCoordinator信息。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.twoPhaseCommitCoordinator.lsid

~~The session identifier for the multi-shard transaction.~~多分片事务的会话标识符。

~~The combination of the lsid and txnNumber identifies the transaction.~~lsid和txnNumber的组合标识事务。

~~Available for both the commit coordination metrics and for specific coordination operation.~~可用于提交协调度量和特定协调操作。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.twoPhaseCommitCoordinator.txnNumber

~~The transaction number for the multi-shard transaction.~~多分片事务的事务编号。

~~The combination of the txnNumber and lsid identifies the transaction.~~txnNumber和lsid的组合标识事务。

~~Available for both the commit coordination metrics and for specific coordination operation.~~可用于提交协调度量和特定协调操作。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.twoPhaseCommitCoordinator.action

~~The specific commit coordination operation spawned by the transaction coordinator:~~事务协调器派生的特定提交协调操作：

"sendingPrepare"
"sendingCommit"
"sendingAbort"
"writingParticipantList"
"writingDecision"
"deletingCoordinatorDoc"

~~Only available for specific coordination operation.~~仅适用于特定的协调操作。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.twoPhaseCommitCoordinator.startTime

~~The start date and time of the action.~~action的开始日期和时间。

~~Only available for specific coordination operation.~~仅适用于特定的协调操作。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.twoPhaseCommitCoordinator.numParticipants

~~Number of shards participating in this commit.~~参与此提交的分片数。

~~Only available for the commit coordination metrics.~~仅适用于提交协调度量。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.twoPhaseCommitCoordinator.state

~~The current step/state of the commit coordination process.~~提交协调过程的当前步骤/状态。

~~Step/stage~~步骤、阶段	~~Description~~描述
`inactive`	~~Not actively part of a commit.~~未主动参与承诺。
`writingParticipantList`	~~Writing a local record of the list of shards that are part of this multi-shard transaction.~~编写属于此多分片事务的分片列表的本地记录。
`waitingForVotes`	~~Waiting for the participants to respond with vote to commit or abort.~~等待参与者通过投票做出响应以提交或中止。
`writingDecision`	~~Writing a local record of the coordinator's decision to commit or abort based on votes.~~编写协调员根据投票决定提交或中止的本地记录。
`waitingForDecisionAck`	~~Waiting for participants to acknowledge the coordinator's decision to commit or abort.~~等待参与者确认协调员提交或中止的决定。
`deletingCoordinatorDoc`	~~Deleting the local record of commit decision.~~删除提交决定的本地记录。

~~Only available for the commit coordination metrics.~~仅适用于提交协调度量。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.twoPhaseCommitCoordinator.commitStartTime

~~The date and time when the commit started.~~提交开始的日期和时间。

~~Only available for the commit coordination metrics.~~仅适用于提交协调度量。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.twoPhaseCommitCoordinator.hasRecoveredFromFailover

~~A boolean that indicates whether the commit coordination was restarted due to failover on the shard that is coordinating the commit.~~一个布尔值，指示是否由于协调提交的分片上的故障转移而重新启动了提交协调。

~~If hasRecoveredFromFailover is true, then the times specified in $currentOp.twoPhaseCommitCoordinator.stepDurations may not be accurate for all steps.~~如果hasRecoveredFromFailover为true，则$currentOp.twoPhaseCommitCoordinator.stepDurations中指定的时间可能不适用于所有步骤。

~~Only available for the commit coordination metrics.~~仅适用于提交协调度量。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.twoPhaseCommitCoordinator.stepDurations

~~A document that contains the duration, in microseconds, of the completed or in-progress steps/state of the active process as well as the cumulative total duration;~~ 一种文档，包含活动过程的已完成或正在进行的steps/state的持续时间（以微秒为单位）以及累计总持续时间；~~for example:~~例如：

"stepDurations" : {
   "writingParticipantListMicros" : NumberLong(17801),
   "totalCommitDurationMicros" : NumberLong(42488463),
   "waitingForVotesMicros" : NumberLong(30378502),
   "writingDecisionMicros" : NumberLong(15015),
   "waitingForDecisionAcksMicros" : NumberLong(12077145),
   "deletingCoordinatorDocMicros" : NumberLong(6009)
},

~~If $currentOp.twoPhaseCommitCoordinator.hasRecoveredFromFailover is true, then the times specified in stepDurations may not be accurate for all steps.~~如果$currentOp.twoPhaseCommitCoordinator.hasRecoveredFromFailover为true，则stepDurations中指定的时间可能不适用于所有步骤。

~~For a coordinator in an inactive state, the document is empty:~~对于处于inactive状态的协调员，文档为空：

"stepDurations" : {
}

~~Only available for the commit coordination metrics.~~仅适用于提交协调度量。

~~See $currentOp.twoPhaseCommitCoordinator.state.~~请参阅$currentOp.twoPhaseCommitCoordinator.state。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.twoPhaseCommitCoordinator.decision

~~A document that contains the commit/abort decision, for example:~~包含提交/中止决定的文档，例如：

~~For a commit decision:~~对于提交决定：

"decision" : {
   "decision" : "commit",
   "commitTimestamp" : Timestamp(1572034669, 3)
}

~~For an abort decision:~~对于中止决定：

"decision" : {
   "decision" : "abort",
   "abortStatus" : {
      "code" : 282,
      "codeName" : "TransactionCoordinatorReachedAbortDecision",
      "errmsg" : "Transaction exceeded deadline"
   }
}

~~Only available for the commit coordination metrics.~~仅适用于提交协调度量。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.twoPhaseCommitCoordinator.deadline

~~The date and time by which the commit must finish.~~提交必须完成的日期和时间。

~~Only available for the commit coordination metrics.~~仅适用于提交协调度量。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.currentOpTime: ~~The start time of the operation.~~操作的开始时间。

$currentOp.effectiveUsers: ~~An array that contains a document for each user associated with the operation.~~ 一个数组，包含与操作相关联的每个用户的文档。~~Each user document contains the user name and the authentication db.~~每个用户文档都包含user名称和身份验证数据库。

Tip

~~See also:~~ 另请参阅：

$currentOp.runBy

$currentOp.runBy

~~An array that contains a document for each user who is impersonating the effectiveUser(s) for the operation.~~ 一个数组，其中包含模拟操作的effectiveUser(s)的每个用户的文档。~~The runBy document contains the user name and the authentication db.~~ runBy文档包含user名称和身份验证db。~~In general, the impersonating user is the __system user; e.g.~~通常，模拟用户是__system用户；例如。

"runBy" : [
   {
      "user" : "__system",
      "db" : "local"
   }
]

$currentOp.opid: ~~The identifier for the operation. You can pass this value to db.killOp() in mongosh to terminate the operation.~~操作的标识符。您可以将此值传递给mongosh中的db.killOp()以终止操作。

Warning

~~Terminate running operations with extreme caution. Only use db.killOp() to terminate operations initiated by clients and do not terminate internal database operations.~~终止运行操作时要格外小心。仅使用db.killOp()终止客户端启动的操作，而不终止内部数据库操作。

$currentOp.secs_running

~~The duration of the operation in seconds.~~ 操作的持续时间（秒）。~~MongoDB calculates this value by subtracting the current time from the start time of the operation.~~MongoDB通过从操作的开始时间减去当前时间来计算这个值。

~~Only present if the operation is running; i.e. if active is true.~~仅在操作正在运行时出现；即如果active为true。

$currentOp.microsecs_running

~~The duration of the operation in microseconds. MongoDB calculates this value by subtracting the current time from the start time of the operation.~~操作的持续时间（以微秒为单位）。MongoDB通过从操作的开始时间减去当前时间来计算这个值。

~~Only present if the operation is running; i.e. if active is true.~~仅在操作正在运行时出现；即如果active为true。

$currentOp.lsid

~~The session identifier.~~会话标识符。

~~Only present if the operation is associated with a session.~~仅当操作与会话关联时才显示。

$currentOp.transaction

~~A document that contains multi-document transaction information.~~包含多文档事务信息的文档。

~~Only present if the operation is part of a transaction:~~仅当操作是事务的一部分时存在：

~~Present starting in 4.0 for transactions on a replica set.~~从4.0开始，在副本集上的事务上呈现。
~~Present starting in 4.2 for transactions on a sharded cluster if $currentOp is run without localOps: true. The transaction information is per shard.~~从4.2开始，如果$currentOp在没有localOps: true的情况下运行，则在分片集群的事务上呈现。事务信息是按分片的。
~~Present starting in 4.2.1 for transactions on a sharded cluster if $currentOp is run with localOps: true.~~ 从4.2.1开始，如果$currentOp与localOps: true一起运行，则为分片集群上的事务呈现。~~The transaction information is a composite view rather than per shard.~~事务信息是一个复合视图，而不是每个分片。

$currentOp.transaction.parameters

~~A document that contains information on multi-document transaction.~~包含多文档事务信息的文档。

~~Only present if the operation is part of a multi-document transaction.~~仅当操作是多文档事务的一部分时才显示。

$currentOp.transaction.parameters.txnNumber

~~The transaction number.~~事务记录编号。

~~Only present if the operation is part of a multi-document transaction.~~仅当操作是多文档事务的一部分时才显示。

$currentOp.transaction.parameters.autocommit

~~A boolean flag that indicates if autocommit is on for the transaction.~~指示事务是否启用自动提交的布尔标志。

~~Only present if the operation is part of a multi-document transaction.~~仅当操作是多文档事务的一部分时才显示。

$currentOp.transaction.parameters.readConcern

~~The read concern for the transaction.~~事务的读取关注。

~~Multi-document transactions support read concern "snapshot", "local", and "majority".~~多文档事务支持读取关注"snapshot"、"local"和"majority"。

~~Only present if the operation is part of a multi-document transaction.~~仅当操作是多文档事务的一部分时才显示。

$currentOp.transaction.globalReadTimestamp

~~The timestamp of the snapshot read by the operations in the sharded cluster transaction that uses "snapshot" read concern.~~ 使用“快照”读取关注的分片集群事务中的操作读取的快照的时间戳。For transactions on sharded clusters, the read concern "snapshot" of the data is synchronized across shards; i.e. other read concerns cannot guarantee that the data is from the same snapshot view across the shards.对于分片集群上的事务，数据的读取关注"snapshot"是跨分片同步的；即，其他读取关注不能保证数据来自分片之间的同一快照视图。

~~Only present when run with localOps: true for sharded cluster transactions.~~仅在针对分片集群事务使用localOps: true运行时才显示。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.transaction.readTimestamp

~~The timestamp of the snapshot being read by the operations in this transaction~~此事务中的操作正在读取的快照的时间戳

~~Only present if the operation is part of a multi-document transaction.~~ 仅当操作是多文档事务的一部分时才显示。~~However, the field is not returned if:~~但是，如果出现以下情况，则不会返回该字段：

~~the transaction is on a sharded cluster and uses "snapshot" read concern, and~~事务位于分片集群上，并使用"snapshot"读取关注，并且
~~$currentOp is run with localOps: true.~~$currentOp使用localOps:true运行。

~~Instead, $currentOp.transaction.globalReadTimestamp is returned.~~并且返回$currentOp.transaction.globalReadTimestamp。

$currentOp.transaction.startWallClockTime

~~The date and time (with time zone) of the transaction start.~~事务开始的日期和时间（带时区）。

~~Only present if the operation is part of a multi-document transaction.~~仅当操作是多文档事务的一部分时才显示。

$currentOp.transaction.timeOpenMicros

~~The duration, in microseconds, for the transaction.~~事务的持续时间（以微秒为单位）。

~~The timeActiveMicros value added to the timeInactiveMicros should equal the timeOpenMicros.~~添加到timeActiveMicros的timeInactiveMicros值应等于timeOpenMicros。

~~Only present if the operation is part of a multi-document transaction.~~仅当操作是多文档事务的一部分时才显示。

$currentOp.transaction.timeActiveMicros

~~The total amount of time that the transaction has been active; i.e. when the transaction had operations running.~~事务处于活动状态的总时间；即当事务运行操作时。

~~The timeActiveMicros value added to the timeInactiveMicros should equal the timeOpenMicros.~~添加到timeInactiveMicros的timeActiveMicros值应等于timeOpenMicros。

~~Only present if the operation is part of a multi-document transaction.~~仅当操作是多文档事务的一部分时才显示。

$currentOp.transaction.timeInactiveMicros

~~The total amount of time that the transaction has been inactive; i.e. when the transaction had no operations running.~~事务处于非活动状态的总时间；即当事务没有运行任何操作时。

~~The timeInactiveMicros value added to the timeActiveMicros should equal the timeOpenMicros.~~添加到timeActiveMicros的timeInactiveMicros值应等于timeOpenMicros。

~~Only present if the operation is part of a multi-document transaction.~~仅当操作是多文档事务的一部分时才显示。

$currentOp.transaction.numParticipants

~~Number of shards participating in this transaction.~~参与此事务的分片数。

~~Only present if the operation is part of a transaction on a sharded cluster and $currentOp is run with localOps: true~~仅当操作是分片集群上事务的一部分并且$currentOp使用localOps:true运行时才存在

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.transaction.participants

An array of documents detailing the participating shards in this transaction. Each document contains the name, a flag indicating if the shard acts as the commit coordinator, and a flag indicating if the shard is only involved in read operations for the transaction.一组详细说明此事务中参与分片的文档。每个文档都包含名称、一个指示分片是否充当提交协调器的标志，以及一个指示分片是否只参与事务的读取操作的标志。

{
   "name" : "shardA",
   "coordinator" : false,
   "readOnly" : false
}

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.transaction.numReadOnlyParticipants

~~Number of shards only affected by read operations in this transaction.~~此事务中仅受读取操作影响的分片数。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.transaction.numNonReadOnlyParticipants

~~Number of shards affected by operations other than reads in this transaction.~~此事务中受读取以外的操作影响的分片数。

~~New in version 4.2.1.~~ 4.2.1版新增。

$currentOp.transaction.expiryTime

~~The date and time (with time zone) when the transaction will time out and abort.~~事务超时和中止的日期和时间（带时区）。

~~The $currentOp.transaction.expiryTime equals the $currentOp.transaction.startWallClockTime + the transactionLifetimeLimitSeconds.~~$currentOp.transaction.expiryTime等于$currentOp.transaction.startWallClockTime+transactionLifetimeLimitSeconds。

~~For more information, see Runtime Limit for transactions.~~有关详细信息，请参阅事务的运行时限制。

~~Only present if the operation is part of a multi-document transaction.~~仅当操作是多文档事务的一部分时才显示。

$currentOp.op

~~A string that identifies the specific operation type. Only present if $currentOp.type is op.~~标识特定操作类型的字符串。仅在$currentOp.type为op时存在。

~~The possible values are:~~可能的值为：

"none"
"update"
"insert"
"query"
"command"
"getmore"
"remove"
"killcursors"

~~"command" operations include most commands such as the createIndexes, aggregate, and findAndModify.~~"command"操作包括大多数命令，如createIndexes、aggregate和findAndModify。

~~"query" operations include find operations and OP_QUERY operations.~~"query"操作包括find操作和OP_QUERY操作。

$currentOp.ns: ~~The namespace the operation targets.~~ 操作的目标命名空间。~~A namespace consists of the database name and the collection name concatenated with a dot (.); that is, "<database>.<collection>".~~名称空间由数据库名称和集合名称组成，集合名称用句点（.）连接；即"<database>.<collection>"。

$currentOp.command

~~A document containing the full command object associated with this operation.~~包含与此操作关联的完整命令对象的文档。

~~For example, the following output contains the command object for a find operation on a collection named items in a database named test:~~例如，以下输出包含对名为test的数据库中名为items的集合执行find操作的命令对象：

"command" : {
  "find" : "items",
  "filter" : {
    "sku" : 1403978
  },
  ...
  "$db" : "test"
}

~~The following example output contains the command object for a getMore operation generated by a command with cursor ID 19234103609 on a collection named items in a database named test:~~以下示例输出包含getMore操作的命令对象，该操作由游标ID为19234103609的命令在名为test的数据库中的名为items的集合上生成：

"command" : {
    "getMore" : NumberLong("19234103609"),
    "collection" : "items",
    "batchSize" : 10,
    ...
    "$db" : "test"
},

~~If the command document exceeds 1 kilobyte, the document has the following form:~~如果命令文档超过1 KB，则该文档具有以下形式：

"command" : {
  "$truncated": <string>,
  "comment": <string>
}

The $truncated field contains a string summary of the document excluding the document's comment field if present. If the summary still exceeds 1 kilobyte then it is further truncated, denoted by an ellipsis (...) at the end of the string.$truncated字段包含文档的字符串摘要，不包括文档的comment字段（如果存在）。如果摘要仍然超过1 KB，则会进一步截断，由字符串末尾的省略号（…）表示。

~~The comment field is present if a comment was passed to the operation. Starting in MongoDB 4.4, a comment may be attached to any database command.~~如果将注释传递给操作，则会出现comment字段。从MongoDB 4.4开始，任何数据库命令都可以附加注释。

$currentOp.cursor

~~A document that contains the cursor information for idleCursor and getmore operations; i.e. where type is idleCursor or op is getmore.~~包含idleCursor和getmore操作的游标信息的文档；即，其中type为idleCursor或op为getmore。

~~If reporting on a getmore operation before the getmore has accessed its cursor information, the cursor field is not available.~~如果在getmore访问其游标信息之前报告getmore操作，则cursor字段不可用。

$currentOp.cursor.cursorId: ~~The ID of the cursor.~~游标的ID。

$currentOp.cursor.createdDate: ~~The date and time when the cursor was created.~~创建游标的日期和时间。

$currentOp.cursor.lastAccessDate

~~The date and time when the cursor was last used.~~上次使用游标的日期和时间。

If the cursor is actively in use (i.e. op is getmore and the type is not idleCursor), then lastAccessDate reports either the time the previous getmore ended or the time the cursor was created if this is the first getmore.如果游标正在使用中（即op是getmore，type不是idleCursor），那么lastAccessDate报告上一个getmore结束的时间，或者如果这是第一个getmore，则报告创建游标的时间。

$currentOp.cursor.nDocsReturned: ~~The cumulative number of documents returned by the cursor.~~游标返回的累计文档数。

$currentOp.cursor.nBatchesReturned: ~~The cumulative number of batches returned by the cursor.~~游标返回的累计批次数。

$currentOp.cursor.noCursorTimeout

~~The flag that indicates that the cursor doesn't timeout when idle; i.e. if the cursor has the noTimeout option set.~~指示游标在空闲时没有超时的标志；即，如果游标设置了noTimeout选项。

~~If true, the cursor does not time out when idle.~~如果为true，则游标在空闲时不会超时。
~~If false, the cursor times out when idle.~~如果为false，则游标在空闲时超时。

Tip

See also: 另请参阅：

$currentOp.cursor.originatingCommand: ~~The originatingCommand field contains the full command object (e.g. find or aggregate) which originally created the cursor.~~originatingCommand字段包含最初创建游标的完整命令对象（例如find或aggregate）。

$currentOp.cursor.planSummary

~~A string that specifies whether the cursor uses a collection scan (COLLSCAN) or an index scan (IXSCAN { ... }).~~一个字符串，用于指定游标是使用集合扫描（COLLSCAN）还是索引扫描（IXSCAN { ... }）。

~~The IXSCAN also includes the specification document of the index used.~~IXSCAN还包括所使用索引的规范文档。

~~Not available when running with localOps: true on mongos or when reporting on idleCursors.~~在mongos上使用localOps: true运行或在idleCursors上报告时不可用。

$currentOp.cursor.operationUsingCursorId

~~The opid of the operation using the cursor.~~使用游标的操作的opid。

~~Only present if the cursor is not idle.~~仅在游标未空闲时出现。

$currentOp.cursor.queryFramework: ~~New in version 6.2.~~ 6.2版新增。

~~A string that specifies the query framework used to process an operation.~~指定用于处理操作的查询框架的字符串。

$currentOp.planSummary

~~Not available when running with localOps: true on mongos.~~在mongos上使用localOps: true运行时不可用。

$currentOp.prepareReadConflicts

~~The number of times the current operation had to wait for a prepared transaction with a write to commit or abort.~~当前操作必须等待准备好的带有写入的事务才能提交或中止的次数。

~~While waiting, the operation continues to hold any necessary locks and storage engine resources.~~在等待期间，操作将继续保留任何必要的锁和存储引擎资源。

$currentOp.writeConflicts: ~~The number of times the current operation conflicted with another write operation on the same document.~~当前操作与同一文档上的另一写入操作冲突的次数。

$currentOp.numYields

numYields ~~is a counter that reports the number of times the operation has yielded to allow other operations to complete.~~是一个计数器，用于报告操作为允许其他操作完成而让步的次数。

~~Typically, operations yield when they need access to data that MongoDB has not yet fully read into memory.~~ 通常情况下，当操作需要访问MongoDB尚未完全读取到内存中的数据时，它们就会屈服。~~This allows other operations that have data in memory to complete quickly while MongoDB reads in data for the yielding operation.~~这允许内存中有数据的其他操作快速完成，同时MongoDB读取数据进行让步操作。

$currentOp.dataThroughputLastSecond

~~Amount of data (in MiB) processed by the validate operation in the last second.~~ validate操作在最后一秒内处理的数据量（MiB）。~~Only available for a validate operation that is currently scanning documents.~~ 仅适用于当前正在扫描文档的validate操作。~~For example:~~例如：

"msg" : "Validate: scanning documents Validate: scanning documents: 7258/24000 30%",
"progress" : {
   "done" : 7258,
   "total" : 24000
},
"numYields" : 0,
"dataThroughputLastSecond" : 15.576952934265137,
"dataThroughputAverage" : 15.375944137573242,

~~New in version 4.4.~~ 4.4版新增。

$currentOp.dataThroughputAverage

~~The average amount of data (in MiB) processed by the validate operation.~~ validate操作处理的平均数据量（以MiB为单位）。~~Only available for a validate operation that is currently scanning documents.~~ 仅适用于当前正在扫描文档的validate操作。~~For example:~~例如：

"msg" : "Validate: scanning documents Validate: scanning documents: 7258/24000 30%",
"progress" : {
   "done" : 7258,
   "total" : 24000
},
"numYields" : 0,
"dataThroughputLastSecond" : 15.576952934265137,
"dataThroughputAverage" : 15.375944137573242,

~~New in version 4.4.~~ 4.4版新增。

$currentOp.waitingForLatch

~~The waitingForLatch document is only available if the operation is waiting to acquire an internal locking primitive (a.k.a. a latch) or for an internal condition to be met.~~waitingForLatch文档仅在操作等待获取内部锁定原语（也称为闩锁）或满足内部条件时可用。

For example,

"waitingForLatch" : {
   "timestamp" : ISODate("2020-03-19T23:25:58.412Z"),
   "captureName" : "FutureResolution",
   "backtrace" : [ ]   // Only if backtrace: true
},

~~Output Field~~输出字段	~~Description~~描述
timestamp	~~The date and time at which the operation started to wait.~~操作开始等待的日期和时间。
captureName	~~The internal name of the section where the operation is currently blocked.~~当前阻止操作的节的内部名称。
backtrace	~~The callstack, if available.~~ 调用堆栈（如果可用）。~~The field is only included if backtrace: true.~~仅当`backtrace:true`时才包括该字段。

~~New in version 4.2.2.~~ 4.2.2版新增。

$currentOp.locks

~~The locks document reports the type and mode of locks the operation currently holds.~~ locks文档报告操作当前持有的锁的类型和模式。~~The possible lock types are as follows:~~可能的锁类型如下：

~~Lock Type~~锁定类型	~~Description~~描述
`ParallelBatchWriterMode`	~~Represents a lock for parallel batch writer mode.~~表示并行批处理写入程序模式的锁。 ~~In earlier versions, PBWM information was reported as part of the `Global` lock information.~~ 在早期版本中，PBWM信息被报告为`Global`锁定信息的一部分。 ~~New in version 4.2.~~ 4.2版新增。
`ReplicationStateTransition`	~~Represents lock taken for replica set member state transitions.~~ 表示副本集成员状态转换的锁定。 ~~New in version 4.2.~~ 4.2版新增。
`Global`	~~Represents global lock.~~表示全局锁。
`Database`	~~Represents database lock.~~表示数据库锁定。
`Collection`	~~Represents collection lock.~~表示集合锁。
`Mutex`	~~Represents mutex.~~表示互斥。
`Metadata`	~~Represents metadata lock.~~表示元数据锁定。
`oplog`	~~Represents lock on the oplog.~~表示oplog上的锁定。

~~The possible modes are as follows:~~可能的模式如下：

~~Lock Mode~~锁定模式	~~Description~~描述
`R`	~~Represents Shared (S) lock.~~表示共享（S）锁。
`W`	~~Represents Exclusive (X) lock.~~表示独占（X）锁。
`r`	~~Represents Intent Shared (IS) lock.~~表示意向共享（IS）锁。
`w`	~~Represents Intent Exclusive (IX) lock.~~表示意向独占（IX）锁。

$currentOp.lockStats

~~For each lock type and mode (see locks for descriptions of lock types and modes), returns the following information:~~对于每个锁类型和模式（请参见locks以了解锁类型和方式的描述），返回以下信息：

$currentOp.lockStats.acquireCount: ~~Number of times the operation acquired the lock in the specified mode.~~操作在指定模式下获取锁的次数。

$currentOp.lockStats.acquireWaitCount: ~~Number of times the operation had to wait for the acquireCount lock acquisitions because the locks were held in a conflicting mode.~~ 由于锁定处于冲突模式，操作必须等待acquireCount锁定获取的次数。~~acquireWaitCount is less than or equal to acquireCount.~~acquireWaitCount小于或等于acquireCount。

$currentOp.lockStats.timeAcquiringMicros

~~Cumulative time in microseconds that the operation had to wait to acquire the locks.~~操作必须等待以获取锁的累计时间（以微秒为单位）。

~~timeAcquiringMicros divided by acquireWaitCount gives an approximate average wait time for the particular lock mode.~~timeAcquiringMicros除以acquireWaitCount得出特定锁定模式的近似平均等待时间。

$currentOp.lockStats.deadlockCount: ~~Number of times the operation encountered deadlocks while waiting for lock acquisitions.~~操作在等待获取锁时遇到死锁的次数。

$currentOp.waitingForLock: ~~Returns a boolean value.~~ 返回布尔值。~~waitingForLock is true if the operation is waiting for a lock and false if the operation has the required lock.~~如果操作正在等待锁，则waitingForLock为true；如果操作具有所需的锁，则为false。

$currentOp.msg: ~~The msg provides a message that describes the status and progress of the operation. In the case of indexing or mapReduce operations, the field reports the completion percentage.~~msg提供一条消息，描述操作的状态和进度。在索引或mapReduce操作的情况下，该字段报告完成百分比。

$currentOp.progress

~~Reports on the progress of mapReduce or indexing operations.~~ 报告mapReduce或索引操作的进度。~~The progress fields corresponds to the completion percentage in the msg field.~~ progress字段对应于msg字段中的完成百分比。~~The progress specifies the following information:~~progress指定了以下信息：

$currentOp.progress.done: ~~Reports the number of work items completed.~~报告已完成的工作项数。

$currentOp.progress.total: ~~Reports the total number of work items.~~报告工作项的总数。

$currentOp.killPending: ~~Returns true if the operation is currently flagged for termination.~~ 如果操作当前被标记为终止，则返回true。~~When the operation encounters its next safe termination point, the operation terminates.~~当操作遇到下一个安全终止点时，操作将终止。

$currentOp.waitingForFlowControl: ~~A boolean that indicates if the operation had to wait because of flow control.~~一个布尔值，指示操作是否由于流控制而必须等待。

$currentOp.flowControlStats

~~The flow control statistics for this operation.~~此操作的流控制统计信息。

$currentOp.flowControlStats.acquireCount: ~~The number of times this operation acquired a ticket.~~此操作获取票证的次数。

$currentOp.flowControlStats.acquireWaitCount: ~~The number of times this operation waited to acquire a ticket.~~此操作等待获取票证的次数。

$currentOp.flowControlStats.timeAcquiringMicros: ~~The total time this operation has waited to acquire a ticket.~~此操作等待获取票证的总时间。

$currentOp.totalOperationTimeElapsed

~~The total time elapsed, in seconds, for the current resharding operation.~~ 当前重新分片操作所用的总时间（以秒为单位）。~~The time is set to 0 when a new resharding operation starts.~~新的重新分片操作开始时，时间设置为0。

~~Only present if a resharding operation is taking place.~~只有在进行重新分片操作时才出现。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.remainingOperationTimeEstimated

~~The estimated time remaining in seconds for the current resharding operation.~~ 当前重新分片操作的估计剩余时间（以秒为单位）。~~The time is set to -1 when a new resharding operation starts.~~新的重新分片操作开始时，时间设置为-1。

~~Only present when a resharding operation is taking place.~~ 仅在进行重新分片操作时出现。~~This field may not be present if an estimate cannot not be computed.~~如果无法计算估计值，则此字段可能不存在。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.approxDocumentsToCopy

~~The approximate number of documents to be copied from the donor shards to the recipient shards during the resharding operation.~~ 在重新分片操作期间，要从供体分片复制到接收方分片的文档的大致数量。~~This number is an estimate that is set at the beginning of the resharding operation and does not change after it has been set.~~ 此数字是在重新分片操作开始时设置的估计值，在设置后不会更改。~~The number is set to 0 when a new resharding operation starts.~~ 当新的重新分片操作开始时，该数字设置为0。It is possible for $currentOp.documentsCopied and $currentOp.bytesCopied to end up exceeding $currentOp.approxDocumentsToCopy and $currentOp.approxBytesToCopy, respectively, if the post-resharding data distribution is not perfectly uniform.如果重新分片后的数据分布不是完全一致的，则$currentOp.documentsCopied和$currentOp.bytesCopied最终可能分别超过$currentOp.approxDocumentsToCopy和$currentOp.approxBytesToCopy。

~~Only present on a recipient shard when a resharding operation is taking place.~~仅在进行重新分片操作时出现在收件人分片上。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.documentsCopied

~~The number of documents copied form donor shards to recipient shards during the resharding operation.~~ 在重新分片操作期间，从施主分片复制到接收者分片的文档数。~~The number is set to 0 when a new resharding operation starts.~~当新的重新分片操作开始时，该数字设置为0。

~~Only present on a recipient shard when a resharding operation is taking place.~~仅在进行重新分片操作时出现在收件人分片上。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.approxBytesToCopy

~~The approximate number of bytes to be copied from the donor shards to the recipient shards during the resharding operation.~~ 在重新分片操作期间，要从供体分片复制到接收方分片的大致字节数。~~This number is an estimate that is set at the beginning of the resharding operation and does not change after it has been set.~~ 此数字是在重新分片操作开始时设置的估计值，在设置后不会更改。The number is set to 0 when a new resharding operation starts. It is possible for $currentOp.documentsCopied and $currentOp.bytesCopied to end up exceeding $currentOp.approxDocumentsToCopy and $currentOp.approxBytesToCopy, respectively, if the post-resharding data distribution is not perfectly uniform.当新的重新分片操作开始时，该数字设置为0。如果重新分片后的数据分布不是完全一致的，则$currentOp.documentsCopied和$currentOp.bytesCopied最终可能分别超过$currentOp.approxDocumentsToCopy和$currentOp.approxBytesToCopy。

~~Only present on a recipient shard when a resharding operation is taking place.~~仅在进行重新分片操作时出现在收件人分片上。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.bytesCopied

~~The number of bytes copied from donor shards to recipient shards during the resharding operation.~~ 在重新分片操作期间从施主分片复制到接收者分片的字节数。~~The number is set to 0 when a new resharding operation starts.~~当新的重新分片操作开始时，该数字设置为0。

~~Only present on a recipient shard when a resharding operation is taking place.~~仅在进行重新分片操作时出现在收件人分片上。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.totalCopyTimeElapsed

~~The total elapsed time, in seconds, for ongoing data copy tasks from donor shards to recipient shards for the current resharding operation.~~ 当前重新分片操作中从施主分片到接收者分片的正在进行的数据复制任务的总运行时间（以秒为单位）。~~The time is set to 0 when a new resharding operation starts.~~新的重新分片操作开始时，时间设置为0。

~~Only present on a recipient shard when a resharding operation is taking place.~~仅在进行重新分片操作时出现在收件人分片上。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.oplogEntriesFetched

~~The number of entries fetched from the oplog for the current resharding operation.~~ 从oplog中为当前重新分片操作提取的条目数。~~The number is set to 0 when a new resharding operation starts.~~当新的重新分片操作开始时，该数字设置为0。

~~Only present on a recipient shard when a resharding operation is taking place.~~仅在进行重新分片操作时出现在收件人分片上。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.oplogEntriesApplied

~~The number of entries applied to the oplog for the current resharding operation.~~ 应用于当前重新分片操作的oplog的条目数。~~The number is set to 0 when a new resharding operation starts.~~当新的重新分片操作开始时，该数字设置为0。

~~Only present on a recipient shard when a resharding operation is taking place.~~仅在进行重新分片操作时出现在收件人分片上。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.totalApplyTimeElapsed

~~The total elapsed time, in seconds, for the apply step of the current resharding operation.~~ 当前重新分片操作的应用步骤的总运行时间（以秒为单位）。~~In the apply step, recipient shards apply oplog entries to modify their data based on new incoming writes from donor shards.~~ 在应用步骤中，接收方分片应用oplog条目，以基于来自施主分片的新传入写入来修改其数据。~~The time is set to 0 when a new resharding operation starts.~~新的重新分片操作开始时，时间设置为0。

~~Only present on a recipient shard when a resharding operation is taking place.~~仅在进行重新分片操作时出现在收件人分片上。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.countWritesDuringCriticalSection

~~The number of writes performed in the critical section for the current resharding operation.~~ 在关键部分中为当前重新分片操作执行的写入次数。~~The critical section prevents new incoming writes to the collection currently being resharded.~~ 关键部分防止对当前正在重新分片的集合进行新的传入写入。~~The number is set to 0 when a new resharding operation starts.~~当新的重新分片操作开始时，该数字设置为0。

~~Only present on a donor shard when a resharding operation is taking place.~~仅在进行重新分片操作时出现在施主分片上。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.totalCriticalSectionTimeElapsed

~~The total elapsed time, in seconds, for the critical section of the current resharding operation.~~ 当前重新分片操作的关键部分的总运行时间（以秒为单位）。~~The critical section prevents new incoming writes to the collection currently being resharded. The time is set to 0 when a new resharding operation starts.~~关键部分防止对当前正在重新分片的集合进行新的传入写入。新的重新分片操作开始时，时间设置为0。

~~Only present on a donor shard when a resharding operation is taking place.~~仅在进行重新分片操作时出现在施主分片上。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.donorState

~~The current state of a donor shard for the resharding operation. The state is set to unused when a new resharding operation starts.~~用于重新分片操作的施主分片的当前状态。当新的重新分片操作开始时，状态设置为unused。

~~Only present on a donor shard when a resharding operation is taking place.~~仅在进行重新分片操作时出现在施主分片上。

~~State~~状态	~~Description~~描述
`unused`	~~The resharding operation is about to start or recovering from a primary failover.~~重新分片操作即将启动或从主故障转移中恢复。
`preparing-to-donate`	~~The donor shard is preparing to donate data to the recipient shards.~~捐赠方分片正准备将数据捐赠给接收方分片。
`donating-initial-data`	~~The donor shard is donating data to the recipient shards.~~施主分片正在向接收者分片捐赠数据。
`donating-oplog-entries`	~~The donor shard is donating oplog entries to the recipient shards.~~施主分片正在向接收者分片捐赠oplog条目。
`preparing-to-block-writes`	~~The donor shard is about to prevent new incoming write operations to the collection that is being resharded.~~施主分片将阻止对正在重新分片的集合进行新的传入写入操作。
`error`	~~An error occurred during the resharding operation.~~重新分片操作期间出错。
`blocking-writes`	~~The donor shard is preventing new incoming write operations and the donor shard has notified all recipient shards that new incoming writes are prevented.~~施主分片正在阻止新的传入写入操作，并且施主分片已通知所有接收方分片阻止了新的传入写操作。
`done`	~~The donor shard has dropped the old sharded collection and the resharding operation is complete.~~供体分片已经丢弃了旧的分片集合，并且重新分片操作已经完成。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.recipientState

~~The current state of a recipient shard for a resharding operation. The state is set to unused when a new resharding operation starts.~~重新分片操作的接收方分片的当前状态。当新的重新分片操作开始时，状态设置为unused。

~~Only present on a donor shard when a resharding operation is taking place.~~仅在进行重新分片操作时出现在施主分片上。

~~State~~状态	~~Description~~描述
`unused`	~~The resharding operation is about to start or recovering from a primary failover.~~重新分片操作即将启动或从主故障转移中恢复。
`awaiting-fetch-timestamp`	~~The recipient shard is waiting for the donor shards to be prepared to donate their data.~~接收方分片正在等待捐赠者分片准备捐赠其数据。
`creating-collection`	~~The recipient shard is creating the new sharded collection.~~接收方分片正在创建新的分片集合。
`cloning`	~~The recipient shard is receiving data from the donor shards.~~接收方分片正在从施主分片接收数据。
`applying`	~~The recipient shard is applying oplog entries to modify its copy of the data based on the new incoming writes from donor shards.~~接收方分片正在应用oplog条目，以基于来自施主分片的新传入写入来修改其数据副本。
`error`	~~An error occurred during the resharding operation.~~重新分片操作期间出错。
`strict-consistency`	~~The recipient shard has all data changes stored in a temporary collection.~~接收方分片将所有数据更改存储在临时集合中。
`done`	~~The resharding operation is complete.~~重新分片操作已完成。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.coordinatorState

~~The state of the resharding coordinator for the current resharding operation.~~ 当前重新分片操作的重新分片协调器的状态。~~The resharding coordinator is an operation that runs on the config server primary.~~ 重新分片协调器是在config服务器primary上运行的操作。~~The state is set to unused when a new resharding operation starts.~~当新的重新分片操作开始时，状态设置为unused。

~~Only present on the coordinating config server.~~仅存在于协调配置服务器上。

~~State~~状态	~~Description~~描述
`unused`	~~The resharding operation is about to start or recovering from a primary failover.~~重新分片操作即将启动或从主故障转移中恢复。
`initializing`	~~The resharding coordinator has inserted the coordinator document into `config.reshardingOperations` and has added the `reshardingFields` to the `config.collections` entry for the original collection.~~重新分片协调器已将协调员文档插入到`config.reshardingOperations`中，并已将`reshardingFields`添加到原始集合的`config.collections`条目中。
`preparing-to-donate`	~~The resharding coordinator~~ 重新分片协调器 ~~has created a `config.collections` entry for the temporary resharding collection.~~已为临时重新分片集合创建了一个`config.collections`条目。 ~~has inserted entries into `config.chunks` for ranges based on the new shard key.~~已将条目插入到基于新分片键的范围的`config.chunks`中。 ~~has inserted entries into `config.tags` for any zones associated with the new shard key.~~已将条目插入到与新分片键关联的任何区域的`config.tags`中。 ~~The coordinator informs participant shards to begin the resharding operation.~~ 协调器通知参与者分片开始重新分片操作。~~The coordinator then waits until all donor shards have picked a `minFetchTimestamp` and are ready to donate.~~ 然后，协调器等待，直到所有捐赠分片都选择了`minFetchTimestamp`并准备好捐赠。
`cloning`	~~The resharding coordinator informs donor shards to donate data to recipient shards.~~ 重新分片协调器通知捐赠者分片将数据捐赠给接受者分片。~~The coordinator waits for all recipients to finish cloning the data from the donor.~~协调器等待所有收件人完成对来自捐赠者的数据的克隆。
`applying`	~~The resharding coordinator informs recipient shards to modify their copies of data based on new incoming writes from donor shards.~~ 重新分片协调器通知接收方分片根据来自施主分片的新传入写入修改其数据副本。~~The coordinator waits for all recipients to finish applying oplog entries.~~协调器等待所有收件人完成oplog项的应用。
`blocking-writes`	~~The resharding coordinator informs donor shards to prevent new incoming write operations to the collection being resharded.~~ 重新分片协调器通知施主分片，以防止对正在重新分片的集合进行新的传入写入操作。~~The coordinator then waits for all recipients to have all data changes.~~然后，协调器等待所有收件人更改所有数据。
`aborting`	~~An unrecoverable error occurred during the resharding operation or the `abortReshardCollection` command (or the `sh.abortReshardCollection()` method) was run.~~在重新分片操作或运行`abortReshardCollection`命令（或`sh.abortReshardCollection()`方法）期间发生了不可恢复的错误。
`committing`	~~The resharding coordinator removes the `config.collections` entry for the temporary resharding collection.~~ 重新分片协调器将删除临时重新分片集合的`config.collections`条目。~~The coordinator then adds the `recipientFields` to the source collection's entry.~~然后，协调器将`recipientFields`添加到源集合的条目中。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.opStatus

~~The current state of a resharding operation.~~重新分片操作的当前状态。

~~Only present if a resharding operation is taking place.~~ 只有在进行重新分片操作时才出现。~~Once the operation has completed, the operation is removed from currentOp output.~~一旦操作完成，该操作将从currentOp输出中删除。

~~State~~状态	~~Description~~描述
`actively running`	~~The resharding operation is actively running.~~重新分片操作正在积极运行。
`success`	~~The resharding operation has succeeded.~~重新分片操作已成功。
`failure`	~~The resharding operation has failed.~~重新分片操作失败。
`canceled`	~~The resharding operation was canceled.~~重新发分片操作已取消。

~~New in version 5.0.~~ 5.0版新增。

$currentOp.collUuid

~~The UUID of the sampled collection.~~采样集合的UUID。

~~This field only appears on documents related to query sampling.~~ 此字段仅出现在与查询采样相关的文档上。~~For details, see Sampled Queries.~~有关详细信息，请参阅采样查询。

~~New in version 7.0.~~ 7.0版新增。

$currentOp.startTime

~~The time at which query sampling began.~~查询采样开始的时间。

~~New in version 7.0.~~ 7.0版新增。

$currentOp.samplesPerSecond

~~The maximum number of queries to sample per second.~~每秒要采样的最大查询数。

~~Only reported when running $currentOp on mongos.~~仅在mongos上运行$currentOp时报告。

~~New in version 7.0.~~ 7.0版新增。

$currentOp.sampledReadsCount

~~The number of sampled read queries.~~采样的读取查询数。

~~New in version 7.0.~~ 7.0版新增。

$currentOp.sampledWritesCount

~~The number of sampled write queries.~~采样的写入查询数。

~~This field only appears on documents related to query sampling.~~ 此字段仅出现在与查询采样相关的文档上。

~~New in version 7.0.~~ 7.0版新增。

$currentOp.sampledReadsBytes

~~The size of the sampled read queries, in bytes.~~采样读取查询的大小，以字节为单位。

~~On a replica set, this is reported on every mongod.~~在复制集上，每个mongod都会报告这种情况。

~~On a sharded cluster, this only reported on mongod with --shardsvr.~~在一个分片集群上，这只在mongod上报告了--shardsvr。

~~New in version 7.0.~~ 7.0版新增。

$currentOp.sampledWritesBytes

~~The size of the sampled write queries, in bytes.~~采样的写入查询的大小，以字节为单位。

~~On a replica set, this is reported on every mongod.~~在复制集上，每个mongod都会报告这种情况。

~~On a sharded cluster, this only reported on mongod with --shardsvr.~~在一个分片集群上，这只在mongod上报告了--shardsvr。

~~New in version 7.0.~~ 7.0版新增。

← $count (aggregation) $densify (aggregation) →