-
Type: Bug
-
Resolution: Duplicate
-
Priority: Minor - P4
-
None
-
Affects Version/s: 2.2.2
-
Component/s: Replication
-
Environment: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
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())
- duplicates
-
SERVER-19318 currentOp command should return cursor
- Closed
- related to
-
SERVER-8878 db.currentOp() and db.killOp() on a mongos should display the host the op is running on.
- Closed
-
SERVER-34633 Allow $currentOp to retrieve operations from all members of each shard in a cluster
- Closed