[SERVER-1925] space not released when dropping collections w/o restart of mongodb but on restart we can't repair Created: 11/Oct/10  Updated: 17/Mar/11  Resolved: 11/Oct/10

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Kenny Gorman Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Steps to reproduce:

  • Run application and create lots of data
  • Disk starts to get full
  • db.<collectionname>.drop
  • space on OS not freed
  • stop mongodb via kill -2
  • startup mongodb, requires repair
  • repair can not work because of lack of free space
  • this message is in log: http://gist.github.com/620908


 Comments   
Comment by Michael Papile [ 19/Oct/10 ]

I am having the same problem with a sharded cluster. My disk is 74% full and will not repair, so I figured I would drop some of my map reduce tables to get it in. It would be nice if the drop did indeed free the space.

Comment by Kenny Gorman [ 11/Oct/10 ]

Ok, then we will have to:

  • fix issue on slave where we can tolerate the interruption
  • bring up slave let it sync up
  • promote to master
  • fix old master

This means we have to get pretty good with promotion techniques in replica sets.

Comment by Eliot Horowitz (Inactive) [ 11/Oct/10 ]

dropping collections is not designed to free space right now.
once we do compaction - it might be possible to add that

Generated at Thu Feb 08 02:58:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.