[SERVER-7591] MongoDB cannot write to disk, it should be able to shut down gracefully with a meaningful error Created: 08/Nov/12 Updated: 10/Dec/14 Resolved: 15/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mark porter | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
During network issues at a cloud provider, the storage on an instance failed. As a result, MongoDB could not write to disk but it would not step down (failover to another node). There were some issues with the Secondary not being a common point due to the network issues, however, such i/o issues should cause an immediate shutdown of the primary so the secondary can come up sooner and downtime (for the overall application) is reduced. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 15/Jan/14 ] |
|
Dup of |