[SERVER-308] option for separate directory per db Created: 22/Sep/09 Updated: 12/Jul/16 Resolved: 26/Jan/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eliot Horowitz (Inactive) | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Minor Change |
| Participants: |
| Description |
|
/data/db/foo/foo.1 |
| Comments |
| Comment by Aaron Staple [ 26/Jan/10 ] |
|
Added --directoryperdb cmd line option Note: On startup, we no longer delete all subdirs of dbpath starting with 'tmp' since that's a legitimate db name prefix. Instead, we store temp repair data in directories starting with '$' and delete any such directories on startup. |
| Comment by auto [ 26/Jan/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by auto [ 26/Jan/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by auto [ 26/Jan/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by Eliot Horowitz (Inactive) [ 26/Jan/10 ] |
|
it doesn't need to be sticky with the db path or check for conflicting files. so if you have /data/db/foo/foo.ns that's fine - and you'll only be able to access 1 of them given startup parameters. |
| Comment by Aaron Staple [ 26/Jan/10 ] |
|
Does this option need to be sticky with the db path, or can we assume the user will specify the correct mode when starting each mongod instance? Do we need to check if preexisting files in the dbpath are consistent with the requested mode? |