repairDatabase should not require twice the disk space in use by databases

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.6.4
    • Component/s: Storage
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Hi, when a lot of documents are inserted then deleted from a database the compaction can be done but disk space in use is not freed back to OS. The repairDatabase always require a lot of free space on disk to work, even if the size of remaining documents and indexes is a fraction of initial files sizes. repairDatabase or equivalent should be able to require free disk space to proceed using the size of remaining data and not the one of current data files.
      Regards.

              Assignee:
              Unassigned
              Reporter:
              Laurent Glayal
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: