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

db.currentOp() doesn't show which user ran the query

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying
    • None
    • Query
    • ALL
    • Hide
      1. Run any mongo query that will run for more than a few seconds.
      2. Run db.currentOp({})

      Notice that the output doesn't include which account ran the query.

      Show
      Run any mongo query that will run for more than a few seconds. Run db.currentOp({}) Notice that the output doesn't include which account ran the query.
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In MongoDB 3.4, the command db.currentOp() doesn't show which mongo user is running the query. This information is critical to being able to call db.killOp() from the original account to kill a query - provided we don't have access to a superadmin account that can kill any query, such is the case of Mongo Atlas customers.

            Assignee:
            backlog-server-query Backlog - Query Team (Inactive)
            Reporter:
            brad@mixmax.com Brad Vogel
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None