[SERVER-32301] Windows shell does not offer to kill current op when terminating Created: 13/Dec/17 Updated: 06/Dec/22 Resolved: 17/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 3.4.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andre Spiegel | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | move-stm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Tooling & Methods
|
| Operating System: | Windows |
| Participants: |
| Description |
|
When there is a long-running operation in the shell on Windows, typing Ctrl-C does not produce the question whether the operation should be terminated. The operation keeps running after the shell is terminated, forcing the user to use db.currentOp() / db.killOp(). The shell should ask the same question as it does in the Unix version. |
| Comments |
| Comment by Robert Guo (Inactive) [ 17/Dec/20 ] |
|
We will no longer be adding new features to the old mongo shell outside of a small number of exceptions. Please consider switching to the new shell, mongosh, for general use cases. If this ticket is desired for MongoDB Server development, please reopen. |