-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.4.1
-
Component/s: Sharding
-
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.
- duplicates
-
SERVER-29546 Add hostname to standard $currentOp output, and include shard name when run on a cluster
- Closed
- is related to
-
SERVER-8136 allow db.currentOp() from mongos to show the query jobs performed on secondaries
- Closed
-
SERVER-96446 Killop for killing an op on a specific shard doesn't work on sharded clusters
- Needs Scheduling