.dropCollection() potential bug

There seems to be a bug where doing .dropCollection() and then immediately recreating the collection does not seem to release space back to OS. This was encountered where a collection was dropped and immediately remade with the same indexes in order to free space. But this then required a server restart in order for the space to be released back to the OS.

The MongoDB server was in a replica set.

Is this a known bug?

It might be a bug. Please open a report at jira.percona.com with details so the dev team can take a look

hi @rkamath have you been able to create a bug for this?

I created it here although I’m not sure if this was the right place or not.

Perfect! It’s in the right project - thank you - I was not able to find it. I’ll provide you an update as soon as I can.

1 Like