-
Type: Improvement
-
Resolution: Won't Fix
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Replication
If there is no persisted data on disk there is no need for a lock file. Creating a lock creates more failure states than are needed.
Likewise there is no need for a dbpath option.
- is duplicated by
-
SERVER-9143 Could not start mongodb arbiter after hard reset because of mongod.lock exist.
- Closed
- related to
-
SERVER-3831 journal by default is unreasonable for an arbiter
- Closed