[SERVER-9923] mmapV1 blocks writes to all databases if filesystem hosting one database is full Created: 13/Jun/13 Updated: 06/Dec/22 Resolved: 14/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MMAPv1, Storage |
| Affects Version/s: | 2.4.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 3 |
| Labels: | pull-request | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | See linked support ticket for details on how to reproduce. |
||||||||||||
| Participants: | |||||||||||||
| Description |
|
The FileAllocator assumes that all storage for databases is shared. If it detects that it cannot allocate more space it moves to the "failed" mode and writes are rejected. This is not the correct behavior if the user has configured mongod with the --directoryPerDb option, since in that model the storage availability for each DB may differ. |