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
- duplicates
-
SERVER-4984 make it possible to interrupt operations in mongos
- Closed