[SERVER-39235] Support SE-based 2-phase drop for SE's not supporting recoveryToTimestamp Created: 28/Jan/19  Updated: 06/Dec/22  Resolved: 09/May/19

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

Type: Improvement Priority: Major - P3
Reporter: Geert Bosch Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-40129 DropPendingCollectionReaper::dropColl... Closed
is depended on by SERVER-38606 Stop allowing NamespaceNotFound error... Backlog
Related
is related to SERVER-38985 assume all tables exist in storage en... Closed
is related to SERVER-40114 The repl two-phase collection drop re... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

For --enableReadMajority==0 we still need the repl-based 2-phase drop, and still require strong locks during the second phase. As all storage engines are now KVCatalog based, we can avoid the repl-based method entirely marking the entry in _mdb_catalog as drop-pending, and only drop the ident and remove the catalog entry completely when the drop is majority committed.



 Comments   
Comment by Sara Williamson [ 09/May/19 ]

It's getting too late in the 4.2 release cycle to make this catalog change. If we still need to do this in 4.4 we will re-open.

Comment by Eric Milkie [ 05/Apr/19 ]

If we mark the entry as drop-pending, doesn't that introduce an upgrade/downgrade issue?

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