Details
-
Improvement
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
Storage Execution
Description
Currently the repairDatabase command takes a global lock, see this code line.
I couldn't find a ticket to track the request to downgrade this to a database level lock, so here it is.
There is a comment referencing SERVER-4328 (db locking) that this is a "TODO" but currently the global lock "may" be necessary due to calling syncDataAndTruncateJournal.
After the storage changes we need to review if a downgrade to a db lock is an option. This would make repairs on a database much easier to handle from an operations point of view.
Attachments
Issue Links
- related to
-
DOCS-3838 unclear locking behavior when repairing a database
-
- Closed
-
-
SERVER-14716 tab-complete blocks under global lock, signals (e.g. SIGSTOP) not handled
-
- Closed
-