$currentOp (aggregation stage)（聚合阶段）

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，请使用管理数据库上的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. 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.$currentOp阶段在文档流上返回一个游标，每个文档流都报告一个操作。每个操作文档都受16MB BSON限制，但与currentOp命令不同，对结果集的总体大小没有限制。

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

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

{ $currentOp: { } }

Constraints约束条件

Examples示例

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

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

{
   "type" : "idleSession",
   "host" : "example.mongodb.com:27017",
   "desc" : "inactive transaction",
   "client" : "198.51.100.1:50428",
   "connectionId" : Long(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" : Long(4),
         "autocommit" : false,
         "readConcern" : {
            "level" : "snapshot",
            "afterClusterTime" : Timestamp(1563892246, 1)
         }
      },
      "readTimestamp" : Timestamp(0, 0),
      "startWallClockTime" : "2019-07-23T10:30:49.461-04:00",
      "timeOpenMicros" : Long(1913590),
      "timeActiveMicros" : Long(55),
      "timeInactiveMicros" : Long(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" : Long(5)
         }
      },
      "Global" : {
         "acquireCount" : {
            "r" : Long(3),
            "w" : Long(1)
         }
      },
      "Database" : {
         "acquireCount" : {
            "r" : Long(2),
            "w" : Long(1)
         }
      },
      "Collection" : {
         "acquireCount" : {
            "w" : Long(1)
         }
      },
      "Mutex" : {
         "acquireCount" : {
            "r" : Long(3)
         }
      },
      "oplog" : {
         "acquireCount" : {
            "r" : Long(2)
         }
      }
   },
   "waitingForFlowControl" : false,
   "flowControlStats" : {},
}

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" : Long(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" : Long(2),
         "autocommit" : false,
         "readConcern" : {
            "level" : "snapshot",
            "afterClusterTime" : Timestamp(1571869019, 2)
         }
      },
      "globalReadTimestamp" : Timestamp(1571869019, 2),
      "startWallClockTime" : "2019-10-23T18:16:59.341-04:00",
      "timeOpenMicros" : Long(169244639),
      "timeActiveMicros" : Long(535),
      "timeInactiveMicros" : Long(169244104),
      "numParticipants" : 2,
      "participants" : [
         {
            "name" : "shardB",
            "coordinator" : true,
            "readOnly" : false
         },
         {
            "name" : "shardA",
            "coordinator" : false,
            "readOnly" : false
         }
      ],
      "numReadOnlyParticipants" : 0,
      "numNonReadOnlyParticipants" : 2
   }
}

{
   "shard" : "shardB",
   "type" : "idleSession",
   "host" : "shardB.mongodb.com:27018",
   "desc" : "inactive transaction",
   "client_s" : "198.51.100.1:53961",
   "connectionId" : Long(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" : Long(1),
         "autocommit" : false,
         "readConcern" : {
            "level" : "snapshot"
         }
      },
      "readTimestamp" : Timestamp(0, 0),
      "startWallClockTime" : "2019-10-21T18:31:12.192-04:00",
      "timeOpenMicros" : Long(24137008),
      "timeActiveMicros" : Long(52),
      "timeInactiveMicros" : Long(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" : Long(3)
         }
      },
      "Global" : {
         "acquireCount" : {
            "r" : Long(1),
            "w" : Long(1)
         }
      },
      "Database" : {
         "acquireCount" : {
            "r" : Long(1),
            "w" : Long(1)
         }
      },
      "Collection" : {
         "acquireCount" : {
            "r" : Long(1),
            "w" : Long(1)
         }
      },
      "Mutex" : {
         "acquireCount" : {
            "r" : Long(6)
         }
      }
   }
}
{
   "shard" : "shardA",
   "type" : "idleSession",
   ...
}

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

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

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

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

const db = client.db("admin");

const pipeline = [
  {
    $currentOp: {
      allUsers: true,
      idleSessions: true
    }
  },
  {
    $match: {
      active: false,
      transaction: { $exists: true }
    }
  }
];

const cursor = db.aggregate(pipeline);
return cursor;

const db = client.db("admin");

const pipeline = [
  {
    $currentOp: {
      allUsers: true,
      idleSessions: true
    }
  },
  { $match: { type: "idleSession" } }
];

const cursor = db.aggregate(pipeline);
return cursor;

const db = client.db("admin");

const pipeline = [
  {
    $currentOp: {
      allUsers: true,
      localOps: true
    }
  },
  { $match: { desc: "query analyzer" } }
];

const cursor = db.aggregate(pipeline);
return cursor;

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，则$currentOpop提供有关特定操作的详细信息。

$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.对于多文档事务，$currentOpclient在事务中存储有关最近运行操作的客户端的信息。

$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. An operation can be active even if the operation has yielded to another operation.一个布尔值，指定操作是否已开始。如果操作已启动，则值为true；如果操作处于空闲状态，例如空闲连接、非活动会话或当前处于空闲状态的内部线程，则该值为false。即使操作已被另一个操作所取代，该操作也可以处于活动状态。

$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或分片成员上运行）仅返回分片当前正在协调的事务的分片协调信息。

The following example filters 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不会返回处于非活动状态的$currentOptwoPhaseCommitCoordinator信息

• If access control is enabled and allUsers: false, $currentOp does not return $currentOp.twoPhaseCommitCoordinator information.如果启用了访问控制并且allUsers: false，则$currentOp不会返回$currentOp.twoPhaseCommitCoordinator信息。

$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.可用于提交协调度量和特定协调操作。

$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.可用于提交协调度量和特定协调操作。

$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.仅适用于特定的协调操作。

$currentOp.twoPhaseCommitCoordinator.startTime

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

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

$currentOp.twoPhaseCommitCoordinator.numParticipants

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

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

$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.仅适用于提交协调指标。

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

$currentOp.twoPhaseCommitCoordinator.commitStartTime

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

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

$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.仅适用于提交协调指标。

$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:包含活动进程的已完成或正在进行的步骤/状态的持续时间（以微秒为单位）以及累计总持续时间的文档；例如：

"stepDurations" : {
   "writingParticipantListMicros" : Long(17801),
   "totalCommitDurationMicros" : Long(42488463),
   "waitingForVotesMicros" : Long(30378502),
   "writingDecisionMicros" : Long(15015),
   "waitingForDecisionAcksMicros" : Long(12077145),
   "deletingCoordinatorDocMicros" : Long(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。

$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.仅适用于提交协调指标。

$currentOp.twoPhaseCommitCoordinator.deadline

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

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

$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

$currentOp.runBy

$currentOp.runBy

An array that contains a document for each user who is impersonating the effectiveUser(s) for the operation. The runBy document contains the user name and the authentication db. In general, the impersonating user is the __system user; e.g.一个数组，其中包含每个模拟操作effectiveUser(s)（有效用户）的用户的文档。runBy文档包含用户名和身份验证数据库。一般来说，冒充用户是__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.versionContext

Describes the Feature Compatibility Version (FCV) of the operation, which the server uses to determine available features.描述操作的功能兼容性版本（FCV），服务器使用该版本确定可用功能。

This information is intended for troubleshooting issues encountered while updating or downgrading a server.此信息用于排除更新或降级服务器时遇到的问题。

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

$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:仅当操作是事务的一部分时才存在：

• On a replica set.在副本集上。
• On a sharded cluster if $currentOp is run without localOps:true. The transaction information is per shard.在分片集群上，如果$currentOp在没有localOps:true的情况下运行。事务信息是按分片的。
• On a sharded cluster if $currentOp is run with localOps:true. The transaction information is a composite view rather than per shard.在分片集群上，如果$currentOp在有localOps:true的情况下运行。事务信息是一个复合视图，而不是每个分片。

$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. 使用"snapshot"读取关注的分片集群事务中的操作读取的快照的时间戳。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运行时存在。

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

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一起运行时才存在

$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
}

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

$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一起运行时才存在

$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一起运行时才存在

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

$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操作的命令对象，该操作由名为test的数据库中名为items的集合上游标ID为19234103609的命令生成：

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

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

"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字段包含文档的字符串摘要，不包括文档的注释字段（如果存在）。如果摘要仍然超过1千字节，则进一步截断，由字符串末尾的省略号（…）表示。

The comment field is present if a comment was passed to the operation. A comment may be attached to any database command.如果向操作传递了注释，则会出现comment字段。任何数据库命令都可以附加注释。

$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.如果为真，游标在空闲时不会超时。
• If false, the cursor times out when idle.如果为false，则游标在空闲时超时。

Tip

cursor.addOption()

$currentOp.cursor.tailable

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

• find
• cursor.tailable()
• cursor.addOption()

$currentOp.cursor.awaitData

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.

Tip

• find
• cursor.tailable()
• cursor.addOption()

$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

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

$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. This allows other operations that have data in memory to complete quickly while MongoDB reads in data for the yielding operation.通常，当操作需要访问MongoDB尚未完全读入内存的数据时，它们会屈服。这允许在内存中有数据的其他操作快速完成，而MongoDB读取数据以进行屈服操作。

$currentOp.queryShapeHash

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

queryShapeHash is a hexadecimal string with the hash of a query shape. For details, see Query Shapes.queryShapeHash是一个十六进制字符串，具有查询形状的哈希值。有关详细信息，请参阅查询形状。

$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. For example:仅适用于当前正在扫描文档的validate（操作）。例如：

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

$currentOp.dataThroughputAverage

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

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

$currentOp.locks

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

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（全局）锁信息的一部分进行报告。
ReplicationStateTransition	Represents lock taken for replica set member state transitions.表示为副本集成员状态转换所采取的锁。
Global	Represents global lock.表示全局锁。
Database	Represents database lock.表示数据库锁。
Collection	Represents collection lock.表示集合锁。
Mutex	Represents mutex.表示互斥体。
Metadata	Represents metadata lock.表示元数据锁。
DDLDatabase	Represents a DDL database lock.表示DDL数据库锁。 New in version 7.1.在版本7.1中新增。
DDLCollection	Represents a DDL collection lock.表示DDL集合锁。 New in version 7.1.在版本7.1中新增。
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.小于或等于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. The progress fields corresponds to the completion percentage in the msg field. The progress specifies the following information:报告mapReduce或索引操作的进度。progress字段对应于msg字段中的完成百分比。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. When the operation encounters its next safe termination point, the operation terminates.如果操作当前被标记为终止，则返回true。当操作遇到下一个安全终止点时，操作终止。

$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. The number is set to 0 when a new resharding operation starts.从oplog中获取的当前重新分片操作的条目数。当新的重新分片操作开始时，该数字设置为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. The number is set to 0 when a new resharding operation starts.应用于oplog以进行当前重新分片操作的条目数。当新的重新分片操作开始时，该数字设置为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. The time is set to 0 when a new resharding operation starts.当前重新分片操作的应用步骤的总耗时（秒）。在应用步骤中，受体分片应用oplog条目，以根据来自供体分片的新写入修改其数据。新的重新分片操作开始时，时间设置为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.用于重新分片操作的供体分片的当前状态。当新的重新分片操作开始时，状态设置为未使用。

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. The state is set to unused when a new resharding operation starts.当前重新分片操作的换牌协调器的状态。重新分片协调器是在配置服务器primary上运行的操作。当新的重新分片操作开始时，状态设置为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条目中。
preparing-to-donate	The resharding coordinator重新分片协调器 has created a config.collections entry for the temporary已为临时数据库创建了config.collections条目 resharding collection.重新分片集合。 has inserted entries into config.chunks for ranges based on the已将基于以下内容的范围的条目插入到config.chunks中 new shard key.新的分片键。 has inserted entries into config.tags for any zones associated已将条目插入到任何关联区域的配置标签中 with the new shard key.使用新的分片键。 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.
committing	The resharding coordinator removes the config.collections entry for the temporary resharding collection. The coordinator then adds the recipientFields to the source collection's entry.重新分片协调器删除临时重新分片集合的config.collections条目。然后，协调器将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.queues

Information about the current operation's ingress and execution queues.有关当前操作ingress（入口）和execution（执行）队列的信息。

$currentOp.queues.isHoldingTicket

Indicates whether the operation currently holds a ticket.指示操作当前是否持有票证。

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

$currentOp.startTime

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

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

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时报告。

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

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

$currentOp.sampledReadsCount

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

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

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.在复制品集上，每个蒙古人都会报告这一点。

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

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

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.在分片集群上，这只报告了带有--shardsvr的mongod。

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

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