-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Query
-
Query 2018-01-29
The aggregation framework pipeline components can run in either mongod or mongos, depending on whether they operate on grouped (or sorted) documents. For SERVER-4844, code was added that would enable interruption of aggregation operations via currentOp/killOp. However, this doesn't work in mongos, because there's no provision for doing that there. Something needs to be created that can be used in the implementation of the InterruptStatusMongos class (in interrupt_status_mongos.cpp).
- depends on
-
SERVER-7210 Consolidate internal mongos interfaces
- Closed
- is duplicated by
-
SERVER-22827 Weird behaviour of currentOp()/killOp() in sharded configurations
- Closed
- is related to
-
SERVER-4844 can't killop an aggregation operation
- Closed
-
SERVER-6496 provide a way to kill a sharded query on all shards
- Closed
-
SERVER-18094 currentOp on a mongoS should also show current mongoS operations
- Closed
-
SERVER-32307 Make AsyncResultsMerger kill sequence issue killCursors without waiting for outstanding batches
- Closed
-
SERVER-33462 Allow killop on a mongos op id
- Closed
- related to
-
SERVER-21004 Implement wait objects that support operation interruption/expiration
- Closed