[SERVER-3931] Shell hangs on tab complete if db is fsync&locked Created: 23/Sep/11  Updated: 17/Feb/17  Resolved: 17/Feb/17

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: 1.8.2, 2.0.0
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Jared Rosoff Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

tested on mac os x & ubuntu 10.4


Issue Links:
Related
related to SERVER-8579 Consolidate Mongod Lock/Resource Sche... Closed
is related to SERVER-4277 Creating new shell while fsync locked... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

1) start mongod
2) start mongo shell
3) shell> db.getSisterDB('admin').runCommand(

{fsync:1,lock:1}

);
4) shell> db.getS <tab>
5) shell hangs.
6) start another shell
7) unlock the db
8) first shell unhangs



 Comments   
Comment by Mira Carey [ 17/Feb/17 ]

fsync lock is a very aggressive command to run on your server and it's not unexpected that certain operations may hang when the server is otherwise occupied.

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