ns field in curop is blank for pending write ops

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.4.0-rc0
    • Component/s: Diagnostics
    • None
    • Query
    • Fully Compatible
    • ALL
    • Hide

      You can see this in the output if you run jstests/currentOp.js

      Show
      You can see this in the output if you run jstests/currentOp.js
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      For read contexts we set the curop ns field at Context construction time.
      For write, we set the field when we "enter" the lock, which means while the lock is still queued you get a CurOp document that looks something like this:

      	{
      		"opid" : 119,
      		"active" : false,
      		"op" : "update",
      		"ns" : "",
      		"query" : {
      			"$where" : function () { sleep(150); }
      		},
      		"client" : "127.0.0.1:49343",
      		"desc" : "conn3",
      		"threadId" : "0x7fb1720af700",
      		"connectionId" : 3,
      		"locks" : {
      			"^test" : "W"
      		},
      		"waitingForLock" : true,
      		"numYields" : 0,
      		"lockStats" : {
      			"timeLockedMicros" : {
      				
      			},
      			"timeAcquiringMicros" : {
      				
      			}
      		}
      	}
      

            Assignee:
            Backlog - Query Team (Inactive)
            Reporter:
            Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: