MongoDB cannot write to disk, it should be able to shut down gracefully with a meaningful error

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

        1. tabeso.log
          2.09 MB
          Angela Shulman

            Assignee:
            Unassigned
            Reporter:
            Mark porter
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: