Priority: Major - P3
Affects Version/s: 3.6.0-rc0
Fix Version/s: None
In a replica set
- create a collection by inserting a document
- restart the replica set
- then drop the collection or database
On the primary the corresponding WT tables may not be dropped, and the .wt file will remain.
The following script reproduces the problem about half the time. The script ends with a loop that waits for the .wt file for the collection to disappear from all members; the problem is reproduced if the loop at the end never terminates and the offending file is associated with the member that was elected as primary. Since the script also reliably reproduces
SERVER-31101, you have to check whether the .wt file associated with the primary remains in order to determine whether this issue has been reproduced. The script prints replica set status before going into the wait loop to help with this.
Note also that the script uses killall -w, so as written will work on Linux but not OSX.