[SERVER-14716] tab-complete blocks under global lock, signals (e.g. SIGSTOP) not handled Created: 29/Jul/14  Updated: 26/Oct/21  Resolved: 26/Oct/21

Status: Closed
Project: Core Server
Component/s: Concurrency, Shell
Affects Version/s: 2.6.3
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Aaron Westendorf Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-3838 unclear locking behavior when repairi... Closed
is related to SERVER-14721 remove global lock from repairDatabas... Closed
Participants:

 Description   

While running a database repair, if you use another mongo shell instance to list current database operations, tab-completing in the mongo shell will lock that shell (and its terminal) until the repair is done or has been killed off.

Even if this behavior is expected, signals such as ctrl-z (SIGTSTP) should allow the user to maintain control over the terminal and if necessary kill the mongo shell.


Generated at Thu Feb 08 03:35:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.