Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-2012

drop fails when unable to allocate

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

      Create a new database and collection in a fresh dbpath, and fill it up. Then try to drop it - there is a file allocation exception.

      Probably related to allocating the freelist namespace.

      We should also check:

      • hitting quota limit
      • dropping an index instead of a ns

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            aaron Aaron Staple
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: