[SERVER-2460] conflict between durability journal directory and database 'journal' directory in directoryperdb mode Created: 01/Feb/11 Updated: 06/Dec/22 Resolved: 20/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Operating System: | ALL |
| Participants: |
| Description |
|
MongoDB shell version: 1.8.0-rc0-pre- > Tue Feb 1 14:26:35 [conn1] dropDatabase journal Abort trap |
| Comments |
| Comment by Dwight Merriman [ 04/May/11 ] |
|
let's disallow new databases with the name journal always - that way they don't exist if you switch to journaling later. just say it's a reserved one? or, disallow journal with directory per db always if you have existing, and this combination is not present, we can still allow, to avoid legacy problems, and just block new creation. |
| Comment by Eliot Horowitz (Inactive) [ 02/Feb/11 ] |
|
we should disallow dbs with the name journal with dur on and db per directory |