As per SERVER-1423, it is possible to fsyncLock() and close the shell, but then not be able to reconnect to the shell in order to fsyncUnlock(). In the docs page for 'fsync' there is a warning that reads may not be possible. It may be necessary to have a more explicit warning that reconnecting to the shell may also not be possible, until SERVER-1423 and surrounding issues are resolved.
- is duplicated by
-
DOCS-1364 Documentation doesn't indicate that db.fsyncLock() uses counters
- Closed
-
DOCS-3681 warn users that fsyncUnlock needs to be issued on same connection as fsyncLock
- Closed
-
DOCS-1638 fsyncLock/Unlock pages should warn about nested calls to fsyncLock
- Closed
- related to
-
SERVER-1423 reads often aren't possible while in fsync and lock mode
- Closed