Details
-
Type:
Technical task
-
Status: Closed
-
Priority:
Minor
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
Usually for extra engines we have <engine> (and the corresponding skip-<engine>) options to control their usage upon server startup. There is no such option for LevelDB, so if one attempts to use it, LevelDB takes it for a prefix of leveldb-lock-wait-timeout, fails to parse it because it doesn't have a value, and aborts on startup.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions