Loading...

XML

Word

Printable

JSON

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v3.6
Steps To Reproduce:
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)); })();
Sprint:
Platforms 2018-01-29, Platforms 2018-02-12

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.

is documented by

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