[SERVER-34553] dropCollection does not free up storage on Secondary Created: 18/Apr/18  Updated: 24/Apr/18  Resolved: 19/Apr/18

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

Type: Bug Priority: Major - P3
Reporter: Manan Shah Assignee: Kelsey Schubert
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-31101 WT table not dropped after collection... Closed
Operating System: ALL
Participants:

 Description   

We dropped a giant collection in a database. It certainly released the storage on the master but all the slaves still has the collection data file xxxxx.wt still lingering on the slaves. There is no replication lag and the logs on the secondary clearly show the drop did went thru the slaves.
2018-04-18T11:25:12.394-0500 I COMMAND [repl writer worker 7] CMD: drop < my big collection name here >

The version of MongoDB we are using is 3.2.19. Please advice.



 Comments   
Comment by Manan Shah [ 19/Apr/18 ]

Oh yes this is in 3.2.12 and not 3.2.19.
Thanks for the recommendation.

Comment by Kelsey Schubert [ 19/Apr/18 ]

Hi manan@indeed.com,

I believe you're encountering SERVER-31101. From the diangostic.data you've uploaded it appears that you are running MongoDB 3.2.12 rather than 3.2.19, which contains this fix. I'd recommend upgrading to a more recent version of MongoDB to resolve this issue.

Kind regards,
Kelsey

Comment by Manan Shah [ 19/Apr/18 ]

Just to update, we had to restart the Secondary instances in order to gain the space back. There were open file handles for the lingering xxxx.wt data file in the OS. Do you know the reason why and if that is a bug, in what version is that resolved?

Comment by Manan Shah [ 18/Apr/18 ]

Thanks Kelsey. All files finished uploading to the portal.

Comment by Kelsey Schubert [ 18/Apr/18 ]

Hi manan@indeed.com,

I believe the JIRA upload limit is currently configured at 150mb, but I've gone ahead and created a secure upload portal for you to use. Files uploaded to this portal are only visible to MongoDB employees investigating this issue and are routinely deleted after some time.

Kind regards,
Kelsey

Comment by Manan Shah [ 18/Apr/18 ]

Sure, even the zipped version is 104M. Basically, zip or gzip didn't help on the diagnostic.data folder. Is it ok to upload 100M file to JIRA or do you prefer some other way of sending you the files?

Comment by Kelsey Schubert [ 18/Apr/18 ]

Hi manan@indeed.com,

Thank you for reporting this issue. So we can investigate, would you please upload an archive of the diagnostic.data from the dbpath of an affected secondary?

Thank you,
Kelsey

Generated at Thu Feb 08 04:37:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.