Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-32498

"desc" field in currentOp output no longer contains the thread name used in log messages

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.6.0
    • 3.6.4, 3.7.2
    • Admin
    • None
    • Fully Compatible
    • ALL
    • v3.6
    • Hide 

      python buildscripts/resmoke.py currentop_desc.js

      currentop_desc.js

      		 
      (function() {
      		 
          "use strict";
      		 
       
      		 
          let res = assert.commandWorked(db.runCommand({whatsmyuri: 1}));
      		 
          const myUri = res.you;
      		 
       
      		 
          res = assert.commandWorked(db.adminCommand({currentOp: 1, client: myUri}));
      		 
          const threadName = res.inprog[0].desc;
      		 
          const connectionId = res.inprog[0].connectionId;
      		 
       
      		 
          assert.eq("conn" + connectionId, threadName, tojson(res));
      		 
      })();

      Show
      python buildscripts/resmoke.py currentop_desc.js currentop_desc.js ( function () { "use strict" ;   let res = assert.commandWorked(db.runCommand({whatsmyuri: 1})); const myUri = res.you;   res = assert.commandWorked(db.adminCommand({currentOp: 1, client: myUri})); const threadName = res.inprog[0].desc; const connectionId = res.inprog[0].connectionId;   assert.eq( "conn" + connectionId, threadName, tojson(res)); })();
    • Platforms 2018-01-29, Platforms 2018-02-12

    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.

      Attachments

        Issue Links

          is documented by

          Task - A task that needs to be done. DOCS-11324 Docs for SERVER-32498: "desc" field in currentOp output no longer contains the thread name used in log messages

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              jonathan.reams@mongodb.com Jonathan Reams
              max.hirschhorn@mongodb.com Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: