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

db.currentOp() and db.killOp() on a mongos should display the host the op is running on.

XMLWordPrintableJSON

    • Sharding

      Currently when you run db.currentOp on a mongos, it tells me which shard it is running on, but not necessarily which node (replica set member) it is running on. This would be particularly useful when running aggregation framework and mapreduces on secondaries to:

      A: Confirm it is following your read preferences and running in the correct place.

      B: Be able to kill these jobs when they are executing on secondaries.

      Currently, it only gives the current operations on the primaries of each shard and doesn't allow you to kill ops on secondaries without logging on directly to that secondary.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            osmar.olivo Osmar Olivo
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: