[SERVER-51235] Dropped a large DB still the storage didn't got free'd Created: 28/Sep/20  Updated: 27/Oct/23  Resolved: 07/Oct/20

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

Type: Bug Priority: Minor - P4
Reporter: Vikram Yerneni Assignee: Dmitry Agranat
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

QA


Participants:

 Description   

Fellas,

We have a MongoDB Cluster (3 node) setup in our QA with 375 GB storage. One of the DB is using almost 365 GB, so the team decided to clean it up. Somehow they are having issues and they asked me to just drop it and I complied (using the drop database command). After the successful drop, the DB is gone and  it can't be seen from the "show dbs" command in the shell. However the space didn't got free'd from the cluster. Somehow something still holding up 365 GB of storage in there. 

 

Am I missing something here??

 

Thanks

Vikram



 Comments   
Comment by Vikram Yerneni [ 06/Oct/20 ]

This can be closed now.

Comment by Vikram Yerneni [ 06/Oct/20 ]

Fellas, thanks all... The issue got sorted out after a restart. 

Even after dropping a DB, the space technically didn't got "free'd" up. So I ended up bouncing the service and then it showed the correct size of the instance.

 

Thanks!

Comment by Dmitry Agranat [ 06/Oct/20 ]

Hi vikram.yerneni@qomplx.com, what mongoDB version do you use?

Comment by Massimiliano Marcon [ 30/Sep/20 ]

vikram.yerneni@qomplx.com I am going to assume this is a server issue even if you were using mongosh when you saw this behavior so I moved it to the right project.

Generated at Thu Feb 08 05:24:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.