mmapV1 blocks writes to all databases if filesystem hosting one database is full

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.4.4
    • Component/s: MMAPv1, Storage
    • Storage Execution
    • ALL
    • Hide

      See linked support ticket for details on how to reproduce.

      Show
      See linked support ticket for details on how to reproduce.
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Andrew Morrow (Inactive)
            Votes:
            3 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: