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

Weird behaviour of currentOp()/killOp() in sharded configurations

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 3.0.2
    • Component/s: Sharding, Shell
    • None
    • ALL

      We have sharded cluster with one replica set rs1

      When we call db.currentOp() trough mongos
      it returns string in field "opid":"rs1:34234232342", when normally we expect to get number

      db.killOp() doesn't support strings, so we cannot call db.killOp("rs1:34234232342")

      What we understood, we can connect directly to replicaSet and run db.killOp(34234232342) // remove "rs1"

      Then it works.

      But why this cannot be done by mongo router itself? If it knows on which replica set operation is running, then it could route this killOp to appropriate RS. Its understandable that then function killOp() should accept also string, or add new param for replica identification

            Assignee:
            Unassigned Unassigned
            Reporter:
            esarguns Eriks Sarguns
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: