Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11324

Docs for SERVER-32498: "desc" field in currentOp output no longer contains the thread name used in log messages

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.2, 3.6.4
    • 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().

      Note: It is still possible to reconstruct the thread name via the "connectionId" field in the currentOp output.

            Assignee:
            kay.kim@mongodb.com Kay Kim (Inactive)
            Reporter:
            kay.kim@mongodb.com Kay Kim (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              5 years, 51 weeks, 1 day ago