reads often aren't possible while in fsync and lock mode

SERVER-11970 While fsyncLock() to secondary stoping write operations also

• 
• Closed

SERVER-2278 A locked mongod can't access a new database.

• 
• Closed

SERVER-2281 after a {fsync: 1, lock: 1}, "show dbs" hangs

• 
• Closed

SERVER-5533 fsync and lock on a Secondary causes the shell to freeze/hang - worse with auth enabled

• 
• Closed

SERVER-11119 mongod connections hang because of assertion failure

• 
• Closed

SERVER-13541 Freeze using mongo + mongodump + fsyncLock

• 
• Closed

SERVER-7711 fsyncLock() makes mongod unusable if no databases have been opened yet

• 
• Closed

SERVER-12577 mongod hangs on shutdown

• 
• Closed

SERVER-6302 Race condition when multiple fsyncLock() invocations made on a mongod instance.

• 
• Closed

SERVER-15946 replSetStepDown without force argument will fail if secondaries are behind and there is any write load

• 
• Closed

DOCS-1603 Warn that fsyncLock() may prevent being able to log into shell to fsyncUnlock()

• 
• Closed

SERVER-4243 If there is a pending write due to an fsync lock, all reads are blocked

• 
• Closed

SERVER-3950 Add a command to stop/restart replication

• 
• Closed

DOCS-3681 warn users that fsyncUnlock needs to be issued on same connection as fsyncLock

• 
• Closed

SERVER-8579 Consolidate Mongod Lock/Resource Scheduling Logic

• 
• Closed

SERVER-15745 Member should not be electable while fsyncLock'd

• 
• Backlog

SERVER-7948 mongodump should assert that server isn't fsyncLocked

• 
• Closed