[SERVER-4281] isMaster command hangs if db is fsyncLocked and authentication is enabled Created: 14/Nov/11  Updated: 29/Jun/12  Resolved: 16/Nov/11

Status: Closed
Project: Core Server
Component/s: Replication, Security
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
is depended on by SERVER-4277 Creating new shell while fsync locked... Closed
is depended on by SERVER-4237 Enable the full js test suite to run ... Closed
Duplicate
duplicates SERVER-4243 If there is a pending write due to an... Closed
Operating System: ALL
Participants:

 Description   

Steps to reproduce:
-Start mongod with authentication
-fsync lock the database
-try to write something (this shell will hang, make sure you already have another shell open and connected)
-in different shell run db.isMaster(). Shell will hang

Doing the same thing without authentication does not cause it to hang.



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

correct fix is SERVER-4243

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

I'm not sure what the best way to address this is. When using authentication, the isMaster command needs to check if it has permissions to run, and to do that it gets a read lock. When fsync locked with a write pending, the read lock can't be taken, which causes this command to hang. Short of fixing SERVER-4243 I'm not sure there's anything we can do about this...

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