[SERVER-38671] remove server parameter for KV drop-pending ident support Created: 17/Dec/18  Updated: 29/Oct/23  Resolved: 25/Jan/19

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

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-38527 Reduce the number of supports*() func... Closed
Related
related to SERVER-43453 Complete TODO listed in SERVER-38671 Backlog
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2019-02-11
Participants:

 Description   

Remove the server parameter introduced in SERVER-38594

Additionally, RollbackImpl::_resetDropPendingState() will no longer have to call DropPendingCollectionReaper::clearDropPendingState() because drop-pending idents are assumed to be supported when this rollback algorithm is used (the alternative is the rollback via refetch implementation in rs_rollback.cpp).

With the changes in SERVER-38527, we can remove supportsPendingDrops() from the storage engine API layer and use supportsRecoveryTimestamp() instead. Additionally, the kv_storage_engine IDL can be removed as it was only used for "enableKVPendingDrops".



 Comments   
Comment by Githook User [ 25/Jan/19 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-38671 remove server parameter for KV drop-pending ident support
Branch: master
https://github.com/mongodb/mongo/commit/3a1b11c960c6fc9bc5c94e4d5cd58f38c78ca55b

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