-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
RSS Sydney
-
Fully Compatible
-
GregsList - 2024-09-03, PopcornChicken - 2024-09-17, MorningKaraoke 2024-10-01, BananaDuck - 2024-10-15, CookieFloss - 29/10/24
-
200
DropPendingCollectionReaper was introduced during PM-716 (legacy 2 phase drop which requires renaming the dropped collection to system.drops.<collection_name>).
Later that style was replaced by KVDropPendingIdentReaper and PM-1114 (making WT to support 2 phase drop). We will not support storage engines other than WT in the near future, so we should remove DropPendingCollectionReaper and its usage.
Doing this may also get rid of some performance overheads as currently this code is called every time committed snapshot is updated, and it involves taking a mutex (though this is very minor since the mutex isn't contented).
- is related to
-
SERVER-84788 Remove RollbackViaRefetch method
- Closed
- split to
-
SERVER-92839 Remove listCollections' includePendingDrops option
- Backlog
-
SERVER-92363 Remove serverStatus().storageEngine.supportsPendingDrops
- Closed