Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Won't Fix
Priority: Minor - P4
Fix Version/s: None
Affects Version/s: None
Component/s: Replication
Labels:
- arbiter

Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Unassigned
Reporter:: Scott Hernandez (Inactive)
Participants:: Eliot Horowitz, Eric Milkie, Scott Hernandez
Votes:: 1 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Mar 27 2013 05:16:25 PM UTC
Updated:: Dec 10 2014 11:14:55 PM UTC
Resolved:: Mar 28 2013 04:58:21 AM UTC