$currentOp (aggregation)

On this page本页内容

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语法

Changed in version 4.2.在版本4.2中更改。

{ $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 will only report on operations/idle connections/idle cursors/idle sessions belonging to the user who ran the command.如果设置为false，$currentOp将仅报告属于运行该命令的用户的操作/空闲连接/空闲游标/空闲会话。
  • If set to true, $currentOp will report 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.对于强制访问控制的分片集群，需要inprog权限才能运行$currentOp。

Defaults to false.默认为false。

idleConnections

Boolean. 默认。If set to false, $currentOp will only report active operations. 如果设置为false，$currentOp将仅报告活动操作。If set to true, all operations including idle connections will be returned.如果设置为true，将返回所有操作，包括空闲连接。

Defaults to false.默认为false。

idleCursors

Boolean.布尔值。

If set to true, $currentOp will report 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。

New in version 4.2.在版本4.2中新增。

idleSessions

Boolean.布尔值。

  • If set to true, in addition to active/dormant operations, $currentOp will report on:如果设置为true，除了活动/休眠操作外，$currentOp还将报告：

    • Inactive sessions that are holding locks as part of a transaction. 作为事务的一部分持有锁的非活动会话。Each inactive session will appear 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字段中的事务的信息。

      Starting in MongoDB 4.2, information on idle sessions have the type set to "idleSession".从MongoDB 4.2开始，关于空闲会话的信息type设置为"idleSession"。

    • $currentOp.twoPhaseCommitCoordinator in inactivestate$currentOp.twoPhaseCommitCoordinator处于inactive（非活动）状态

  • If set to false, $currentOp will not report on:如果设置为false，$currentOp将不会报告：

Defaults to true.默认为true。

New in version 4.0.在版本4.0中新增。

localOps

Boolean. 布尔值。If set to true for an aggregation running on mongos, $currentOp reports only those operations running locally on that mongos. 如果在mongos上运行的聚合设置为true，$currentOp仅报告在该mongos本地运行的操作。If false, then the $currentOp will instead report 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。

New in version 4.0.在版本4.0中新增。

backtrace

Boolean. 布尔值。Determines whether callstack information is returned as part of the waitingForLatch output field.确定调用堆栈信息是否作为waitingForLatch输出字段的一部分返回。

Defaults to false.默认为false。

New in version 4.2.2.在版本4.2.2中新增。

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

{ $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.对于强制访问控制的分片集群，需要inprog权限才能运行$currentOp。

Transactions事务

Example示例

The following 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 just those 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 } } }
] )

Starting in version 4.2, you can use $currentOp.type to specify an equivalent filter:从版本4.2开始，可以使用$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:两个操作都返回以下格式的文档：

When run on a mongod that is part of a replica set:

{
   "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 shards information) of the in-progress transactions run on that 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. When run without localOps:true on the mongos, the transaction information is per shard.

When run on a mongos without localOps:true, the transaction information is per shard.

{
   "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",
   ...
}

Output Fields输出字段

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

$currentOp.type

New in version 4.2.在版本4.2中新增。

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.有关客户端的其他信息。

For multi-document transactions, $currentOp.client stores information about the most recent client to run an operation inside the transaction.对于多文档事务，$currentOp.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 those transactions currently being coordinated by that shard.提交协调由shard处理，$currentOp（在mongos或shard成员上运行）仅返回当前由该分片协调的事务的分片协调信息。

    To filter for just 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注意

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/stageDescription描述
inactiveNot actively part of a commit.不主动参与提交。
writingParticipantListWriting a local record of the list of shards that are part of this multi-shard transaction.写入作为该多分片事务一部分的分片列表的本地记录。
waitingForVotesWaiting for the participants to respond with vote to commit or abort.等待参与者以投票提交或中止响应。
writingDecisionWriting a local record of the coordinator's decision to commit or abort based on votes.编写协调员根据投票决定提交或中止的本地记录。
waitingForDecisionAckWaiting for participants to acknowledge the coordinator's decision to commit or abort.等待参与者确认协调员的提交或中止决定。
deletingCoordinatorDocDeleting the local record of commit decision.删除提交决策的本地记录。

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

See also $currentOp.twoPhaseCommitCoordinator.stepDurations.另请参见$currentOp.twoPhaseCommitCoordinator.stepDurations。

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; for example:包含活动进程的已完成或正在进行的steps/state的持续时间（微秒）以及累计总持续时间的文档；例如：

"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 commmit decision:对于commmit决策：

    "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.每个用户文档包含用户名和身份验证db。

New in version 4.2.在版本4.2中新增。

Tip提示
See also: 参阅：
$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"
   }
]

New in version 4.2.在版本4.2中新增。

$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. 如果$currentOp在没有localOps: true的情况下运行，则从4.2开始出现在分片集群上的事务。The transaction information is per shard.事务信息是每个分片的。
  • Present starting in 4.2.1 for transactions on a sharded cluster if $currentOp is run with localOps: true. 如果$currentOp以localOps: true运行，则从4.2.1开始出现在分片集群上的事务。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.仅当操作是多文档事务的一部分时存在。

New in version 4.0.在版本4.0中新增。

$currentOp.transaction.parameters.txnNumber

The transaction number.事务编号。

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

New in version 4.0.在版本4.0中新增。

$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.仅当操作是多文档事务的一部分时存在。

New in version 4.0.2.在版本4.0.2中新增。

$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.仅当操作是多文档事务的一部分时存在。

New in version 4.0.2.在版本4.0.2中新增。

$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:但是，如果出现以下情况，则不会返回该字段：

Instead, $currentOp.transaction.globalReadTimestamp is returned.而是返回$currentOp.transaction.globalReadTimestamp。

New in version 4.0.2.在版本4.0.2中新增。

$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.仅当操作是多文档事务的一部分时存在。

New in version 4.0.2.在版本4.0.2中新增。

$currentOp.transaction.timeOpenMicros

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

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.仅当操作是多文档事务的一部分时存在。

New in version 4.0.2.在版本4.0.2中新增。

$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.仅当操作是多文档事务的一部分时存在。

New in version 4.0.2.在版本4.0.2中新增。

$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 shardas in this transaction. 详细说明此事务中参与shardas的一系列文档。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
}

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.numReadOnlyParticipants

Number of shards only affected by read operations 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.numNonReadOnlyParticipants

Number of shards affected by operations other than reads 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.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.

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

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

New in version 4.0.2.在版本4.0.2中新增。

$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.操作包括大多数命令，如createIndexes、aggregate和findAndModify。

"query" operations include find operations and OP_QUERY operations.操作包括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

Changed in version 3.6.在版本3.6中更改。

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. $truncated字段包含文档的字符串摘要，不包括文档的comment字段（如果存在）。If the summary still exceeds 1 kilobyte then it is further truncated, denoted by an ellipsis (...) at the end of the string.如果摘要仍然超过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

New in version 4.2.在版本4.2中新增。

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

New in version 4.2.在版本4.2中新增。

The id of the cursor.游标的id。

$currentOp.cursor.createdDate

New in version 4.2.在版本4.2中新增。

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

$currentOp.cursor.lastAccessDate

New in version 4.2.在版本4.2中新增。

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

New in version 4.2.在版本4.2中新增。

The cumulative number of documents returned by the cursor.游标返回的文档的累积数量。

$currentOp.cursor.nBatchesReturned

New in version 4.2.在版本4.2中新增。

The curmulative number of batches returned by the cursor.游标返回的累计批数。

$currentOp.cursor.noCursorTimeout

New in version 4.2.在版本4.2中新增。

The flag that indicates that the cursor will not 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 will time out when idle.如果为false，则游标将在空闲时超时。
Tip提示
See also: 参阅：
$currentOp.cursor.tailable

New in version 4.2.在版本4.2中新增。

The flag that indicates if the cursor is a tailable cursor for a capped collection. 指示游标是否为带上限集合的可跟踪游标的标志。Tailable cursors remain open after the client exhausts the results in the initial cursor.在客户端耗尽初始游标中的结果后，可定制游标将保持打开状态。

Tip提示
$currentOp.cursor.awaitData

New in version 4.2.在版本4.2中新增。

The flag that indicates whether the tailable cursor should temporarily block a getMore command on the cursor while waiting for new data rather than returning no data.指示可跟踪游标是否应在等待新数据而不是不返回数据时临时阻止游标上的getMore命令的标志。

For non-tailable cursors, the value is always false.对于不可定制的游标，该值始终为false。

Tip提示
$currentOp.cursor.originatingCommand

New in version 4.2.在版本4.2中新增。

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

Note注意

Starting in version 4.2, MongoDB now returns originatingCommand field as a nested field in the new cursor field. 从版本4.2开始，MongoDB现在返回originatingCommand字段作为新游标字段中的嵌套字段。In previous versions, the originatingCommand was a top-level field for the associated "getmore" document.在以前的版本中，originatingCommand是关联"getmore"文档的顶级字段。

$currentOp.cursor.planSummary

New in version 4.2.在版本4.2中新增。

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

New in version 4.2.在版本4.2中新增。

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

Only present if the cursor is not idle.仅当游标不空闲时出现。

$currentOp.planSummary

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

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.等待时，操作将继续保持任何必要的锁和存储引擎资源。

New in version 4.2.在版本4.2中新增。

$currentOp.writeConflicts

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

New in version 4.2.在版本4.2中新增。

$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 FieldDescription描述
timestampThe date and time at which the operation started to wait.操作开始等待的日期和时间。
captureNameThe internal name of the section where the operation is currently blocked.当前阻止操作的节的内部名称。
backtraceThe 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中新增。

GlobalRepresents global lock.表示全局锁。
DatabaseRepresents database lock.表示数据库锁。
CollectionRepresents collection lock.表示集合锁。
MutexRepresents mutex.表示互斥体。
MetadataRepresents metadata lock.表示元数据锁。
oplogRepresents lock on the oplog.表示oplog上的锁。

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

Lock Mode锁定模式Description描述
RRepresents Shared (S) lock.表示共享锁。
WRepresents Exclusive (X) lock.表示独占（X）锁。
rRepresents Intent Shared (IS) lock.表示意图共享（IS）锁。
wRepresents 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.

$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，如果操作具有所需的锁定，则waitingForLock为false。

$currentOp.msg

The msg provides a message that describes the status and progress of the operation. msg提供描述操作状态和进度的消息。In the case of indexing or mapReduce operations, the field reports the completion percentage.对于索引或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 will terminate.当操作遇到下一个安全终止点时，操作将终止。

$currentOp.waitingForFlowControl

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

New in version 4.2.在版本4.2中新增。

$currentOp.flowControlStats

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

New in version 4.2.在版本4.2中新增。

$currentOp.flowControlStats.acquireCount

The number of times this operation acquired a ticket.此操作获取票证的次数。

New in version 4.2.在版本4.2中新增。

$currentOp.flowControlStats.acquireWaitCount

The number of times this operation waited to aqcuire a ticket.此操作等待获取票证的次数。

New in version 4.2.在版本4.2中新增。

$currentOp.flowControlStats.timeAcquiringMicros

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

New in version 4.2.在版本4.2中新增。

$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.仅当正在进行重硬操作时出现。

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. 当开始新的重硬操作时，该数字设置为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.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 perfomed 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.当新的重硬操作开始时，状态设置为未使用。

Only present on a donor shard when a resharding operation is taking place.仅在进行重硬操作时出现在供体分片上。

State状态Description描述
unusedThe resharding operation is about to start or recovering from a primary failover.重新硬盘操作即将启动或从主故障切换中恢复。
preparing-to-donateThe donor shard is preparing to donate data to the recipient shards.捐赠者分片正在准备将数据捐赠给接收者分片。
donating-initial-dataThe donor shard is donating data to the recipient shards.捐赠者分片正在向接收者分片捐赠数据。
donating-oplog-entriesThe donor shard is donating oplog entries to the recipient shards.捐赠者分片正在向接收者分片捐赠oplog条目。
preparing-to-block-writesThe donor shard is about to prevent new incoming write operations to the collection that is being resharded.施主分片将阻止对正在重新硬盘的集合进行新的写入操作。
errorAn error occurred during the resharding operation.重新硬盘操作期间出错。
blocking-writesThe donor shard is preventing new incoming write operations and the donor shard has notified all recipient shards that new incoming writes are prevented.施主分片正在阻止新的传入写入操作，并且施主分片已通知所有接收方分片阻止了新的传入写操作。
doneThe 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描述
unusedThe resharding operation is about to start or recovering from a primary failover.重新硬盘操作即将启动或从主故障切换中恢复。
awaiting-fetch-timestampThe recipient shard is waiting for the donor shards to be prepared to donate their data.接收者分片正在等待捐赠者分片准备捐赠他们的数据。
creating-collectionThe recipient shard is creating the new sharded collection.收件人分片正在创建新的分片集合。
cloningThe recipient shard is receiving data from the donor shards.接收方分片正在从施主分片接收数据。
applyingThe recipient shard is applying oplog entries to modify its copy of the data based on the new incoming writes from donor shards.接收方分片正在应用oplog条目，以基于来自施主分片的新传入写入修改其数据副本。
errorAn error occurred during the resharding operation.oplog重新分片操作期间出错。
strict-consistencyThe recipient shard has all data changes stored in a temporary collection.接收方分片将所有数据更改存储在临时集合中。
doneThe 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. 重新存储协调器是在配置服务器主服务器上运行的操作。The state is set to unused when a new resharding operation starts.当新的重硬操作开始时，状态设置为unused。

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

State状态Description描述
unusedThe resharding operation is about to start or recovering from a primary failover.重新硬盘操作即将启动或从主故障切换中恢复。
initializingThe 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并准备捐赠。

cloningThe 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.协调器等待所有接收者完成从捐赠者克隆数据。
applyingThe 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-writesThe 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.协调器然后等待所有接收者进行所有数据更改。
abortingAn unrecoverable error occurred during the resharding operation or the abortReshardCollection command (or the sh.abortReshardCollection() method) was run.在重新存储操作或运行abortReshardCollection命令（或sh.abortReshardCollection()方法）期间发生了不可恢复的错误。
committingThe 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 runningThe resharding operation is actively running.重新存储操作正在积极运行。
successThe resharding operation has succeeded.重新存储操作已成功。
failureThe resharding operation has failed.重新存储操作失败。
canceledThe resharding operation was canceled.重新硬盘操作已取消。

New in version 5.0.在版本5.0中新增。

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