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

allow db.currentOp() from mongos to show the query jobs performed on secondaries

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor - P4
    • Resolution: Duplicate
    • 2.2.2
    • None
    • Replication
    • Debian 6.0 kernel: Linux 2.6.38-2-amd64
      cluster: a sharded cluster with 4 replica sets. Each rs contains a primary & a secondary & an arbiter
    • Replication
    • Linux

    Description

      I wanted to use db.killOp() to kill some long time queries which were performed on secondaries by using read preference "Secondary".
      But the jobs are not shown when I use db.currentOp() so I can not kill them.
      (Queries performed on primaries can be shown by using db.currentOp())

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-19318 currentOp command should return cursor

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-8878 db.currentOp() and db.killOp() on a mongos should display the host the op is running on.

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-34633 Allow $currentOp to retrieve operations from all members of each shard in a cluster

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

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              strlee stronglee
              Votes:
              4 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: