-
Type:
Improvement
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Query
-
Query 2018-01-29
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
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
-
-
- Closed
-
- is duplicated by
-
SERVER-22827 Weird behaviour of currentOp()/killOp() in sharded configurations
-
- Closed
-
- is related to
-
-
- Closed
-
-
SERVER-6496 provide a way to kill a sharded query on all shards
-
- Closed
-
-
-
- Closed
-
-
SERVER-32307 Make AsyncResultsMerger kill sequence issue killCursors without waiting for outstanding batches
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-