Dropping an index fails when quota exceeded

XMLWordPrintableJSON

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

      When dropping an index, it's possible for the operation to fail due to a "disk space quota exceeded" error. Seems like removal operations that reduce the size of the database shouldn't ever cause this kind of error.

      command failed [command
      failed [drop]

      { "nIndexesWas" : 1.0 , "msg" : "indexes dropped for collection" , "ns" : "xxx.yyy" , "errmsg" : "exception: db disk space quota exceeded xxx" , "code" : 12501 , "ok" : 0.0}

              Assignee:
              Aaron Staple (Inactive)
              Reporter:
              Robert Miyashiro (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: