Details
-
Improvement
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
None
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.
Attachments
Issue Links
- is duplicated by
-
SERVER-9235 Better messaging/logging when disks are inaccessible
-
- Closed
-