-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
Affects Version/s: 2.0.1
-
Component/s: Concurrency
-
None
-
Environment:64bit Ubuntu 11.04 + gcc 4.5.2
-
Linux
By locking the database and issuing a single write, all readers are starved. No read operations can go through.
Because of this, a new shell will start but cannot be used – it must be doing some read-lock requiring operation. Ostensibly, this is due to the shell attempting to read but being unable to do so due to the waiting write starving any reader attempt.
Issuing "mongo --eval 'db.fsyncUnlock()'" will unlock the database, allow writes through, and unfreeze the shell.
- is duplicated by
-
SERVER-4281 isMaster command hangs if db is fsyncLocked and authentication is enabled
- Closed
- is related to
-
SERVER-2278 A locked mongod can't access a new database.
- Closed
-
SERVER-4277 Creating new shell while fsync locked with authentication hangs.
- Closed
-
SERVER-1423 reads often aren't possible while in fsync and lock mode
- Closed