-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
Scope
In master branch
- source/includes/currentOp-output-example.rst:7 "threadId" : <string>
- source/reference/command/currentOp.txt:209 .. data:: currentOp.threadId
- source/reference/method/cursor.comment.txt:131 "threadId" : "0x10772e000"
- 4.0-compatibility mentions the removal, instead of the specific currentOp (pipeline/command/shell helper pages as it doesn't seem that helpful on those pages)
- Backport to 3.6
ToDo work at TBD
We need to audit the currentOp page for 3.6 changes as not sure when last audited and updated wholesale.
Documentation Request Summary:
The currentOp output no longer includes the "threadId" of the thread running the op. This was removed because it can leak sensitive info on some platforms.
Engineering Ticket Description:
Client::_desc is initialized as the string "conn" rather than the string "conn" + session->id().
- https://github.com/mongodb/mongo/blob/r3.6.0/src/mongo/transport/service_state_machine.cpp#L231
- https://github.com/mongodb/mongo/blob/r3.6.0/src/mongo/db/service_context.cpp#L147
- https://github.com/mongodb/mongo/blob/r3.6.0/src/mongo/db/client.cpp#L112
Note: It is still possible to reconstruct the thread name via the "connectionId" field in the currentOp output.
- documents
-
SERVER-32498 "desc" field in currentOp output no longer contains the thread name used in log messages
- Closed