[SERVER-37874] killOp should accept multiple operations Created: 01/Nov/18 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Admin, Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Participants: |
| Description |
|
The killOp command accepts only a single opId. If multiple operations need to be killed, this has to be done with multiple separate calls to killOp. This doesn't scale if there are a large number of problematic operations. By contrast both killSessions and killCursors accept an array of things to kill. It would be useful if killOp could be extended so that in addition to accepting a single opId, it could optionally accept an array of opIds instead. |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 02/Nov/21 ] |
|
Service Arch team is in the process of cleaning up tickets in the backlog. This ticket has not been updated in two years so we are closing it. Please reopen if you think this change is valuable. |