-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.3
-
Component/s: Storage
-
None
I have a replica set of 2 data nodes and 1 arbiter. On primary I ran two commands:
db.fs.files.drop()
db.fs.chunks.drop()
The collections successfully deleted from primary and secondary but they still exist as files in collection directory. How to tell mongodb that they should be removed from disk? Don't want to keep 400Gb of useless data.
- duplicates
-
SERVER-31101 WT table not dropped after collection is dropped due to long-running OperationContext
- Closed