Definition
currentOpReturns a document that contains information on in-progress operations for the
mongodinstance.currentOphas the following form:{ currentOp: 1 } The
mongoshell provides thedb.currentOp()wrapper for thecurrentOpcommand.Note
Because
currentOpcommand anddb.currentOp()helper returns the results in a single document, the total size of thecurrentOpresult set is subject to the maximum 16MB BSON size limit for documents.Starting in version 3.6, MongoDB provides
$currentOpaggregation stage. The$currentOpstage 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 thecurrentOpcommand, there is no limit on the overall size of the result set.For this reason, the
$currentOpaggregation stage is preferred over thecurrentOpcommand and itsmongoshell helperdb.currentOp().
Behavior
currentOp must run against the admin database, and
it can accept several optional fields.
Field | Description |
|---|---|
| Boolean. If set to On New in version 3.2.9. |
| Boolean. If set to
|
<filter> | Specify filter conditions on the Output Fields. See Examples. |
| Optional. A user-provided comment to attach to this command. Once set, this comment appears alongside records of this command in the following locations:
A comment can be any valid BSON type (string, integer, object, array, etc). New in version 4.4. |
currentOp and the
database profiler report the same
basic diagnostic information for all CRUD operations, including the
following:
getMore(OP_GET_MORE andcommand)
These operations are also included in the logging of
slow queries (see slowOpThresholdMs for
more information about slow query logging).
Access Control
On systems running with authorization, the user
must have access that includes the inprog privilege
action.
Users can use
$ownOps on mongod instances to view their own
operations without the inprog privilege action.
db.adminCommand( { currentOp: 1, "$ownOps": 1 } )
Examples
The following examples use the currentOp command with
various query documents to filter the output.
Display All Current Operations
db.adminCommand( { currentOp: true, "$all": true } )
Write Operations Waiting for a Lock
The following example returns information on all write operations that are waiting for a lock:
db.adminCommand( { currentOp: true, "waitingForLock" : true, $or: [ { "op" : { "$in" : [ "insert", "update", "remove" ] } }, { "command.findandmodify": { $exists: true } } ] } )
Active Operations with no Yields
The following example returns information on all active running operations that have never yielded:
db.adminCommand( { currentOp: true, "active" : true, "numYields" : 0, "waitingForLock" : false } )
Active Operations on a Specific Database
The following example returns information on all active operations for
database db1 that have been running longer than 3 seconds:
db.adminCommand( { currentOp: true, "active" : true, "secs_running" : { "$gt" : 3 }, "ns" : /^db1\./ } )
Active Indexing Operations
The following example returns information on index creation operations:
db.adminCommand( { currentOp: true, $or: [ { op: "command", "command.createIndexes": { $exists: true } }, { op: "none", "msg" : /^Index Build/ } ] } )
Output Example
The following is a prototype of the currentOp
output when run on a standalone:
Changed in version 4.2.
{ "inprog": [ { "type" : <string>, "host" : <string>, "desc" : <string>, "connectionId" : <number>, "client" : <string>, "appName" : <string>, "clientMetadata" : <document>, "active" : <boolean>, "currentOpTime" : <string>, "effectiveUsers" : [ { "user" : <string>, "db" : <string> } ], "opid" : <number>, "lsid" : { "id" : <UUID>, "uid" : <BinData> }, "secs_running" : <NumberLong()>, "microsecs_running" : <number>, "op" : <string>, "ns" : <string>, "command" : <document>, "planSummary": <string>, "cursor" : { // only for getMore operations "cursorId" : <NumberLong()>, "createdDate" : <ISODate()>, "lastAccessDate" : <ISODate()>, "nDocsReturned" : <NumberLong()>, "nBatchesReturned" : <NumberLong()>, "noCursorTimeout" : <boolean>, "tailable" : <boolean>, "awaitData" : <boolean>, "originatingCommand" : <document>, "planSummary" : <string>, "operationUsingCursorId" : <NumberLong()> }, "msg": <string>, "progress" : { "done" : <number>, "total" : <number> }, "killPending" : <boolean>, "numYields" : <number>, "dataThroughputLastSecond" : <number>, // Starting in MongoDB 4.4 for validate operations "dataThroughputAverage" : <number>, // Starting in MongoDB 4.4 for validate operations "waitingForLatch" : { // Starting in MongoDB 4.2.2 "timestamp" : <ISODate()>, "captureName" : <string> }, "locks" : { "ParallelBatchWriterMode" : <string>, "ReplicationStateTransition" : <string>, "Global" : <string>, "Database" : <string>, "Collection" : <string>, "Metadata" : <string>, "oplog" : <string> }, "waitingForLock" : <boolean>, "lockStats" : { "ParallelBatchWriterMode" : { "acquireCount": { "r": <NumberLong>, "w": <NumberLong>, "R": <NumberLong>, "W": <NumberLong> }, "acquireWaitCount": { "r": <NumberLong>, "w": <NumberLong>, "R": <NumberLong>, "W": <NumberLong> }, "timeAcquiringMicros" : { "r" : NumberLong(0), "w" : NumberLong(0), "R" : NumberLong(0), "W" : NumberLong(0) }, "deadlockCount" : { "r" : NumberLong(0), "w" : NumberLong(0), "R" : NumberLong(0), "W" : NumberLong(0) } }, "ReplicationStateTransition" : { ... }, "Global": { ... }, "Database" : { ... }, ... } }, ... ], "fsyncLock": <boolean>, "info": <string>, "ok": <num> }
The following is a prototype of the currentOp
output when run on a primary of a replica set:
Changed in version 4.2.
{ "inprog": [ { "type" : <string>, "host" : <string>, "desc" : <string>, "connectionId" : <number>, "client" : <string>, "appName" : <string>, "clientMetadata" : <document>, "lsid" : { "id" : <UUID>, "uid" : <BinData> }, "transaction" : { "parameters" : { "txnNumber" : <NumberLong()>, "autocommit" : <boolean>, "readConcern" : { "level" : <string> } }, "readTimestamp" : <Timestamp>, "startWallClockTime" : <string>, "timeOpenMicros" : <NumberLong()>, "timeActiveMicros" : <NumberLong()>, "timeInactiveMicros" : <NumberLong()>, "expiryTime" : <string>, }, "active" : <boolean>, "currentOpTime" : <string>, "effectiveUsers" : [ { "user" : <string>, "db" : <string> } ], "opid" : <number>, "secs_running" : <NumberLong()>, "microsecs_running" : <number>, "op" : <string>, "ns" : <string>, "command" : <document>, "originatingCommand" : <document>, "planSummary": <string>, "prepareReadConflicts" : <NumberLong()>, "writeConflicts" : <NumberLong()>, "cursor" : { // only for getMore operations "cursorId" : <NumberLong()>, "createdDate" : <ISODate()>, "lastAccessDate" : <ISODate()>, "nDocsReturned" : <NumberLong()>, "nBatchesReturned" : <NumberLong()>, "noCursorTimeout" : <boolean>, "tailable" : <boolean>, "awaitData" : <boolean>, "originatingCommand" : <document>, "planSummary" : <string>, "operationUsingCursorId" : <NumberLong()> }, "msg": <string>, "progress" : { "done" : <number>, "total" : <number> }, "killPending" : <boolean>, "numYields" : <number>, "dataThroughputLastSecond" : <number>, // Starting in MongoDB 4.4 for validate operations "dataThroughputAverage" : <number>, // Starting in MongoDB 4.4 for validate operations "waitingForLatch" : { // Starting in MongoDB 4.2.2 "timestamp" : <ISODate()>, "captureName" : <string> }, "locks" : { "ParallelBatchWriterMode" : <string>, "ReplicationStateTransition" : <string>, "Global" : <string>, "Database" : <string>, "Collection" : <string>, "Metadata" : <string>, "oplog" : <string> }, "waitingForLock" : <boolean>, "lockStats" : { "ParallelBatchWriterMode" : { "acquireCount": { "r": <NumberLong>, "w": <NumberLong>, "R": <NumberLong>, "W": <NumberLong> }, "acquireWaitCount": { "r": <NumberLong>, "w": <NumberLong>, "R": <NumberLong>, "W": <NumberLong> }, "timeAcquiringMicros" : { "r" : NumberLong(0), "w" : NumberLong(0), "R" : NumberLong(0), "W" : NumberLong(0) }, "deadlockCount" : { "r" : NumberLong(0), "w" : NumberLong(0), "R" : NumberLong(0), "W" : NumberLong(0) } }, "ReplicationStateTransition" : { ... }, "Global" : { ... }, "Database" : { ... }, ... } }, ... ], "fsyncLock": <boolean>, "info": <string>, "ok": <num>, "operationTime": <timestamp>, "$clusterTime": <document> }
The following is an example of the currentOp
output when run on a mongos of a sharded
cluster (Fields may vary depending on the operation being
reported):
Changed in version 4.2.
{ "inprog": [ { "shard": <string>, "type" : <string>, "host" : <string>, "desc" : <string>, "connectionId" : <number>, "client_s" : <string>, "appName" : <string>, "clientMetadata" : <document>, "lsid" : { "id" : <UUID>, "uid" : <BinData> }, "transaction" : { "parameters" : { "txnNumber" : <NumberLong()>, "autocommit" : <boolean>, "readConcern" : { "level" : <string> } }, "readTimestamp" : <Timestamp>, "startWallClockTime" : <string>, "timeOpenMicros" : <NumberLong()>, "timeActiveMicros" : <NumberLong()>, "timeInactiveMicros" : <NumberLong()>, "expiryTime" : <string>, }, "active" : <boolean>, "currentOpTime" : <string>, "effectiveUsers" : [ { "user" : <string>, "db" : <string> } ], "runBy" : [ { "user" : <string>, "db" : <string> } ], "twoPhaseCommitCoordinator" : { // Starting in 4.2.1 "lsid" : { "id" : <UUID>, "uid" : <BinData> }, "txnNumber" : <NumberLong>, "numParticipants" : <NumberLong>, "state" : <string>, "commitStartTime" : <ISODate>, "hasRecoveredFromFailover" : <boolean>, "stepDurations" : <document>, "decision" : <document>, "deadline" : <ISODate> } "opid" : <string>, "secs_running" : <NumberLong()>, "microsecs_running" : <number>, "op" : <string>, "ns" : <string>, "command" : <document>, "planSummary": <string>, "prepareReadConflicts" : <NumberLong()>, "writeConflicts" : <NumberLong()>, "cursor" : { // only for getMore operations "cursorId" : <NumberLong()>, "createdDate" : <ISODate()>, "lastAccessDate" : <ISODate()>, "nDocsReturned" : <NumberLong()>, "nBatchesReturned" : <NumberLong()>, "noCursorTimeout" : <boolean>, "tailable" : <boolean>, "awaitData" : <boolean>, "originatingCommand" : <document>, "planSummary" : <string>, "operationUsingCursorId" : <NumberLong()> }, "msg": <string>, "progress" : { "done" : <number>, "total" : <number> }, "killPending" : <boolean>, "numYields" : <number>, "dataThroughputLastSecond" : <number>, // Starting in MongoDB 4.4 for validate operations "dataThroughputAverage" : <number>, // Starting in MongoDB 4.4 for validate operations "waitingForLatch" : { // Starting in MongoDB 4.2.2 "timestamp" : <ISODate()>, "captureName" : <string> }, "locks" : { "ParallelBatchWriterMode" : <string>, "ReplicationStateTransition" : <string>, "Global" : <string>, "Database" : <string>, "Collection" : <string>, "Metadata" : <string>, "oplog" : <string> }, "waitingForLock" : <boolean>, "lockStats" : { "ParallelBatchWriterMode": { "acquireCount": { "r": <NumberLong>, "w": <NumberLong>, "R": <NumberLong>, "W": <NumberLong> }, "acquireWaitCount": { "r": <NumberLong>, "w": <NumberLong>, "R": <NumberLong>, "W": <NumberLong> }, "timeAcquiringMicros" : { "r" : NumberLong(0), "w" : NumberLong(0), "R" : NumberLong(0), "W" : NumberLong(0) }, "deadlockCount" : { "r" : NumberLong(0), "w" : NumberLong(0), "R" : NumberLong(0), "W" : NumberLong(0) } }, "ReplicationStateTransition" : { ... }, "Global" : { ... }, "Database" : { ... }, ... } }, ... ], "ok": <num>, "operationTime": <timestamp>, "$clusterTime": <document> }
Output Fields
currentOp.typeNew in version 4.2.
The type of operation. Values are either:
opidleSessionidleCursor
If the
currentOp.typeisop,currentOp.opprovides details on the specific operation.
currentOp.descA description of the client. This string includes the
connectionId.
currentOp.clientA string with information about where the operation originated.
For multi-document transactions,
clientstores information about the most recent client to run an operation inside the transaction.
currentOp.appNameNew in version 3.4.
The identifier of the client application which ran the operation. Use the
appNameconnection string option to set a custom value for theappNamefield.
currentOp.clientMetadataAdditional information on the client.
For multi-document transactions,
clientstores information about the most recent client to run an operation inside the transaction.
currentOp.effectiveUsersAn array that contains a document for each user associated with the operation. Each user document contains the
username and the authenticationdb.New in version 4.2.
currentOp.runByAn array that contains a document for each user who is impersonating the
effectiveUser(s)for the operation. The runBy document contains theusername and the authenticationdb. In general, the runBy user is the__systemuser; e.g."runBy" : [ { "user" : "__system", "db" : "local" } ] Only available on sharded clusters
New in version 4.2.
currentOp.lsidThe session identifier.
Only present if the operation is associated with a session.
New in version 3.6.
currentOp.transactionA document that contains multi-document transaction information.
Only present if the operation is part of a multi-document transaction.
currentOp.transaction.parametersA document that contains information on multi-document transaction.
Only present if the operation is part of a multi-document transaction.
currentOp.transaction.parameters.txnNumberThe transaction number.
Only present if the operation is part of a multi-document transaction.
currentOp.transaction.parameters.autocommitA 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.readConcernThe read concern for the transaction.
Multi-document transactions support read concern
"snapshot","local", and"majority".Only present if the operation is part of a multi-document transaction.
currentOp.transaction.readTimestampThe timestamp of the snapshot being read by the operations in the transaction.
Only present if the operation is part of a multi-document transaction.
currentOp.transaction.startWallClockTimeThe date and time (with time zone) of the transaction start.
Only present if the operation is part of a multi-document transaction.
currentOp.transaction.timeOpenMicrosThe duration of the transaction in microseconds.
The
timeActiveMicrosvalue added to thetimeInactiveMicrosshould equal thetimeOpenMicros.Only present if the operation is part of a multi-document transaction.
currentOp.transaction.timeActiveMicrosThe total amount of time that the transaction has been active; i.e. when the transaction had operations running.
The
timeActiveMicrosvalue added to thetimeInactiveMicrosshould equal thetimeOpenMicros.Only present if the operation is part of a multi-document transaction.
currentOp.transaction.timeInactiveMicrosThe total amount of time that the transaction has been inactive; i.e. when the transaction had no operations running.
The
timeInactiveMicrosvalue added to thetimeActiveMicrosshould equal thetimeOpenMicros.Only present if the operation is part of a multi-document transaction.
currentOp.transaction.expiryTimeThe date and time (with time zone) when the transaction will time out and abort.
The
currentOp.transaction.expiryTimeequals thecurrentOp.transaction.startWallClockTime+ thetransactionLifetimeLimitSeconds.For more information, seee Runtime Limit for transactions.
Only present if the operation is part of a multi-document transaction.
currentOp.twoPhaseCommitCoordinatorInformation 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 amongosor a shard member) returns a shard's coordination information only for those transactions currently being coordinated by that shard.To filter for just the commit coordination metrics:
db.currentOp( { desc: "transaction coordinator" }) A specific commit coordination operation (i.e.
currentOp.typeisopandcurrentOp.descis"TransactionCoordinator") spawned by the transaction coordinator.
New in version 4.2.1.
currentOp.twoPhaseCommitCoordinator.lsidThe session identifier for the multi-shard transaction.
The combination of the
lsidandtxnNumberidentifies the transaction.Available for both the commit coordination metrics and for specific coordination operation.
New in version 4.2.1.
currentOp.twoPhaseCommitCoordinator.txnNumberThe transaction number for the multi-shard transaction.
The combination of the
txnNumberandlsididentifies the transaction.Available for both the commit coordination metrics and for specific coordination operation.
New in version 4.2.1.
currentOp.twoPhaseCommitCoordinator.actionThe specific commit coordination operation spawned by the transaction coordinator:
"sendingPrepare""sendingCommit""sendingAbort""writingParticipantList""writingDecision""deletingCoordinatorDoc"
Only available for specific coordination operation.
currentOp.twoPhaseCommitCoordinator.startTimeThe start date and time of the
action.Only available for specific coordination operation.
New in version 4.2.1.
currentOp.twoPhaseCommitCoordinator.numParticipantsNumber of shards participating in this commit.
Only available for the commit coordination metrics.
New in version 4.2.1.
currentOp.twoPhaseCommitCoordinator.stateThe current step/state of the commit coordination process.
Step/stageDescriptioninactiveNot 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.New in version 4.2.1.
currentOp.twoPhaseCommitCoordinator.commitStartTimeThe date and time when the commit started.
Only available for the commit coordination metrics.
New in version 4.2.1.
currentOp.twoPhaseCommitCoordinator.hasRecoveredFromFailoverA boolean that indicates whether the commit coordination was restarted due to failover on the shard that is coordinating the commit.
If
hasRecoveredFromFailoveris true, then the times specified incurrentOp.twoPhaseCommitCoordinator.stepDurationsmay not be accurate for all steps.Only available for the commit coordination metrics.
New in version 4.2.1.
currentOp.twoPhaseCommitCoordinator.stepDurationsA document that contains the duration, in microseconds, of the commit coordination
steps/statecompleted or in progress:"stepDurations" : { "writingParticipantListMicros" : NumberLong(17801), "totalCommitDurationMicros" : NumberLong(42488463), "waitingForVotesMicros" : NumberLong(30378502), "writingDecisionMicros" : NumberLong(15015), "waitingForDecisionAcksMicros" : NumberLong(12077145), "deletingCoordinatorDocMicros" : NumberLong(6009) }, If
currentOp.twoPhaseCommitCoordinator.hasRecoveredFromFailoveris true, then the times specified instepDurationsmay not be accurate for all steps.For a coordinator in an
inactivestate, the document is empty:"stepDurations" : { } Only available for the commit coordination metrics.
See
currentOp.twoPhaseCommitCoordinator.state.New in version 4.2.1.
currentOp.twoPhaseCommitCoordinator.decisionA document that contains the commit/abort decision, for example:
For a commmit decision:
"decision" : { "decision" : "commit", "commitTimestamp" : Timestamp(1572034669, 3) } For an abort decision:
"decision" : { "decision" : "abort", "abortStatus" : { "code" : 282, "codeName" : "TransactionCoordinatorReachedAbortDecision", "errmsg" : "Transaction exceeded deadline" } }
Only available for the commit coordination metrics.
New in version 4.2.1.
currentOp.twoPhaseCommitCoordinator.deadlineThe date and time by which the commit must finish.
Only available for the commit coordination metrics.
New in version 4.2.1.
currentOp.opidThe identifier for the operation. You can pass this value to
db.killOp()in themongoshell to terminate the operation.Warning
Terminate running operations with extreme caution. Only use
db.killOp()to terminate operations initiated by clients and do not terminate internal database operations.
currentOp.activeA boolean value specifying whether the operation has started. Value is
trueif the operation has started orfalseif the operation is idle, such as an idle connection or an internal thread that is currently idle. An operation can be active even if the operation has yielded to another operation. For some inactive background threads, such as an inactivesignalProcessingThread, MongoDB suppresses various empty fields.
currentOp.secs_runningThe duration of the operation in seconds. MongoDB calculates this value by subtracting the current time from the start time of the operation.
Only appears if the operation is running; i.e. if
activeistrue.
currentOp.microsecs_runningThe duration of the operation in microseconds. MongoDB calculates this value by subtracting the current time from the start time of the operation.
Only appears if the operation is running; i.e. if
activeistrue.
currentOp.opA string that identifies the specific operation type. Only present if
currentOp.typeisop.The possible values are:
"none""update""insert""query""command""getmore""remove""killcursors"
"query"operations include read operations."command"operations include most commands such as thecreateIndexesandfindAndModify.
currentOp.nsThe namespace the operation targets. A namespace consists of the database name and the collection name concatenated with a dot (
.); that is,"<database>.<collection>".
currentOp.commandA document containing the full command object associated with this operation.
For example, the following output contains the command object for a
findoperation on a collection nameditemsin a database namedtest:"command" : { "find" : "items", "filter" : { "sku" : 1403978 }, ... "$db" : "test" } The following example output contains the command object for a
getMoreoperation generated by a command with cursor ID19234103609on a collection nameditemsin a database namedtest:"command" : { "getMore" : NumberLong("19234103609"), "collection" : "items", "batchSize" : 10, ... "$db" : "test" }, If the command document exceeds 1 kilobyte, the document has the following form:
"command" : { "$truncated": <string>, "comment": <string> } The
$truncatedfield contains a string summary of the document excluding the document'scommentfield if present. If the summary still exceeds 1 kilobyte then it is further truncated, denoted by an ellipsis (...) at the end of the string.The
commentfield is present if a comment was passed to the operation. Starting in MongoDB 4.4, a comment may be attached to any database command.
currentOp.planSummarySpecifies whether the cursor uses a collection scan (
COLLSCAN) or an index scan (IXSCAN { ... }).The
IXSCANalso includes the specification document of the index used.
currentOp.prepareReadConflictsThe number of times the current operation had to wait for a prepared transaction with a write to commit or abort.
While waiting, the current operation continues to hold any necessary locks and storage engine resources.
New in version 4.2.
currentOp.writeConflictsThe number of times the current operation conflicted with another write operation on the same document.
New in version 4.2.
currentOp.cursorNew in version 4.2.
A document that contains the cursor information for
getmoreoperations; i.e. whereopisgetmore.If reporting on a
getmoreoperation before thegetmorehas accessed its cursor information, thecursorfield is not available.currentOp.cursor.nDocsReturnedNew in version 4.2.
The cumulative number of documents returned by the cursor.
currentOp.cursor.nBatchesReturnedNew in version 4.2.
The curmulative number of batches returned by the cursor.
currentOp.cursor.noCursorTimeoutNew in version 4.2.
The flag that indicates that the cursor will not timeout when idle; i.e. if the cursor has the
noTimeoutoption set.If true, the cursor does not time out when idle.
If false, the cursor will time out when idle.
currentOp.cursor.tailableNew in version 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.
currentOp.cursor.awaitDataNew in version 4.2.
The flag that indicates whether the tailable cursor should temporarily block a
getMorecommand on the cursor while waiting for new data rather than returning no data.For non-tailable cursors, the value is always false.
currentOp.cursor.originatingCommandNew in version 4.2.
The
originatingCommandfield contains the full command object (e.g.findoraggregate) which originally created the cursor.Note
Starting in version 4.2, MongoDB now returns
originatingCommandfield as a nested field in the newcursorfield. In previous versions, theoriginatingCommandwas a top-level field for the associated"getmore"document.
currentOp.waitingForLatchThe
waitingForLatchdocument 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.For example,
"waitingForLatch" : { "timestamp" : ISODate("2020-03-19T23:25:58.412Z"), "captureName" : "FutureResolution", }, Output FieldDescriptiontimestamp
The date and time at which the operation started to wait.
captureName
The internal name of the section where the operation is currently blocked.
New in version 4.2.2.
currentOp.locksThe
locksdocument reports the type and mode of locks the operation currently holds. The possible lock types are as follows:Lock TypeDescriptionParallelBatchWriterModeRepresents a lock for parallel batch writer mode.
In earlier versions, PBWM information was reported as part of the
Globallock information.New in version 4.2.
ReplicationStateTransitionRepresents lock taken for replica set member state transitions.
New in version 4.2.
GlobalRepresents global lock.
DatabaseRepresents database lock.
CollectionRepresents collection lock.
MutexRepresents mutex.
MetadataRepresents metadata lock.
oplogRepresents lock on the oplog.
The possible modes are as follows:
Lock ModeDescriptionRRepresents Shared (S) lock.
WRepresents Exclusive (X) lock.
rRepresents Intent Shared (IS) lock.
wRepresents Intent Exclusive (IX) lock.
currentOp.waitingForLockReturns a boolean value.
waitingForLockistrueif the operation is waiting for a lock andfalseif the operation has the required lock.
currentOp.msgThe
msgprovides 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.
currentOp.progressReports on the progress of mapReduce or indexing operations. The
progressfields corresponds to the completion percentage in themsgfield. Theprogressspecifies the following information:
currentOp.killPendingReturns
trueif the operation is currently flagged for termination. When the operation encounters its next safe termination point, the operation will terminate.
currentOp.numYieldsnumYieldsis 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.
currentOp.dataThroughputLastSecondAmount of data (in MiB) processed by the
validateoperation in the last second. Only available for avalidateoperation that is currently scanning documents. 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.
currentOp.dataThroughputAverageThe average amount of data (in MiB) processed by the
validateoperation. Only available for avalidateoperation that is currently scanning documents. 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.
currentOp.fsyncLockSpecifies if database is currently locked for
fsync write/snapshot.Only appears if locked; i.e. if
fsyncLockistrue.
currentOp.infoInformation regarding how to unlock database from
db.fsyncLock(). Only appears iffsyncLockistrue.
currentOp.lockStatsFor each lock type and mode (see
currentOp.locksfor descriptions of lock types and modes), returns the following information:currentOp.lockStats.acquireCountNumber of times the operation acquired the lock in the specified mode.
currentOp.lockStats.acquireWaitCountNumber of times the operation had to wait for the
acquireCountlock acquisitions because the locks were held in a conflicting mode.acquireWaitCountis less than or equal toacquireCount.
currentOp.lockStats.timeAcquiringMicrosCumulative time in microseconds that the operation had to wait to acquire the locks.
timeAcquiringMicrosdivided byacquireWaitCountgives an approximate average wait time for the particular lock mode.
currentOp.waitingForFlowControlA boolean that indicates if the operation is in the process of waiting for flow control.
New in version 4.2.
currentOp.flowControlStatsThe flow control statistics for this operation.
New in version 4.2.
currentOp.flowControlStats.acquireCountThe number of times this operation acquired a ticket.
New in version 4.2.