[SERVER-4984] make it possible to interrupt operations in mongos Created: 16/Feb/12 Updated: 06/Dec/22 Resolved: 02/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Assigned Teams: |
Query
|
||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Query 2018-01-29 | ||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
The aggregation framework pipeline components can run in either mongod or mongos, depending on whether they operate on grouped (or sorted) documents. For |
| Comments |
| Comment by David Storch [ 02/Apr/18 ] | ||||||
|
Hi all, This work is completed and will first be available in the 3.7.4 development release, which will evolve into the 4.0 stable release series. Related ticket
Furthermore, mongos operation IDs are now killable due to the changes in
Finally, 3.7.4 contains related enhancements which will cause sharded queries to quickly clean themselves up on all shards in the case of an error (e.g. | ||||||
| Comment by Ian Boros [ 29/Jan/18 ] | ||||||
|
Once the sharded kill project is complete, we should close this (perhaps as "gone away"). | ||||||
| Comment by Kaloian Manassiev [ 10/Jan/18 ] | ||||||
|
No problem with me. | ||||||
| Comment by David Storch [ 10/Jan/18 ] | ||||||
|
kaloian.manassiev can we move this onto the query team backlog? It's related to a project we're running about improving sharded kill. |