[DOCS-11252] Document the output fields for currentOp when run on a mongos Created: 24/Jan/18  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Louis Williams Assignee: Kay Kim (Inactive)
Resolution: Won't Do Votes: 0
Labels: currentOp, mongod, output
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.mongodb.com/manual/reference/command/currentOp/#currentop-output-fields


Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769
Story Points: 1

 Description   

There is no documentation for what the output fields of currentOp are when run on a mongos, but there is documentation for a mongod: https://docs.mongodb.com/manual/reference/command/currentOp/#currentop-output-fields

The output of currentOp on a mongos is very different than the output on a mongod. The output also varies between different version of MongoDB. It would be helpful for users to understand what information is available, particularly because the server does not support killing queries run on sharded clusters. This is a pain point for many users. See SERVER-6496.

New fields were added in 3.6, in particular command.$client.mongos.client, that allow users to locate the shard and operation IDs for commands originating from a client connection by looking at the host and port.



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Githook User [ 04/Dec/18 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@mongodb.com'}

Message: DOCS-11252: 4.2 currentOp output baseline
Branch: master
https://github.com/mongodb/docs/commit/53c31b2cd7c7da613c95bd25e5f5490435b22ca8

Comment by Githook User [ 04/Dec/18 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@mongodb.com'}

Message: DOCS-11252: 4.0 currentOp output baseline
Branch: v4.0
https://github.com/mongodb/docs/commit/b16a55bb12b98627edc50cac32cba132c89ed99b

Comment by Githook User [ 04/Dec/18 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@mongodb.com'}

Message: DOCS-11252: 3.6 currentOp output baseline
Branch: v3.6
https://github.com/mongodb/docs/commit/1e16a6fa80de58c6f7cda01c593a2ee0534f01e7

Comment by Githook User [ 04/Dec/18 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@mongodb.com'}

Message: DOCS-11252: 3.4 currentOp output
Branch: v3.4
https://github.com/mongodb/docs/commit/d48846cb65a9815ac0199ef5bec03261a62cead4

Comment by Jeffrey Allen [ 24/Jan/18 ]

We could potentially split the currentop page into two separate ones, one for mongod output and one for mongos. This might be helpful in making sure we don't overload the page with too much information, forcing the reader to go back and forth between mongod and mongos contexts.

Generated at Thu Feb 08 08:02:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.