[SERVER-4277] Creating new shell while fsync locked with authentication hangs. Created: 14/Nov/11  Updated: 04/Apr/14  Resolved: 16/Nov/11

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

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-4281 isMaster command hangs if db is fsync... Closed
is depended on by SERVER-4237 Enable the full js test suite to run ... Closed
Related
related to SERVER-3931 Shell hangs on tab complete if db is ... Closed
related to SERVER-4243 If there is a pending write due to an... Closed
Operating System: ALL
Participants:

 Description   

Steps to reproduce:
Start mongod with auth
connect a shell
authenticate against admin db
fsynclock the database
try to insert data - this shell will hang
try to start a new shell, it hangs on startup

This can leave you unable to fsyncUnlock if you accidentally try to write data while fsyncLocked.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 16/Nov/11 ]

correct fix is SERVER-4243

Comment by Spencer Brody (Inactive) [ 14/Nov/11 ]

The problem is that for some reason the isMaster command hangs when the db is fsync locked and authentication is enabled. If the db is fsync locked without authentication (or authentication is on without fsync locking), the isMaster command works fine.

Comment by Spencer Brody (Inactive) [ 14/Nov/11 ]

There is actually an issue specific to using authentication which is that the shell hangs on startup rather than after issuing the first read query, which can leave you unable to fsync unlock.

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