[SERVER-9144] Non-data nodes (arbiter) should not create a lock file Created: 27/Mar/13 Updated: 10/Dec/14 Resolved: 28/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | arbiter | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 28/Mar/13 ] |
|
Arbiters do have state:
I don't think stateless arbiters is something we would want to consider now. |
| Comment by Scott Hernandez (Inactive) [ 27/Mar/13 ] |
|
We do not, no. That would yet another thing... People do use tempfs/ram-disk to back things themselves but that is not what I was thinking. |
| Comment by Eric Milkie [ 27/Mar/13 ] |
|
I don't think we currently have the ability to do non-file-backed MongoFiles |
| Comment by Scott Hernandez (Inactive) [ 27/Mar/13 ] |
|
We need an in-memory only collection for users, replicated normally (at startup). |
| Comment by Eric Milkie [ 27/Mar/13 ] |
|
Not sure we can do this, because of SERVER-5479. We'd have to completely rearchitect the arbiter. |