[SERVER-34069] Postpone 2nd phase of collection drop until drop timestamp is in the stable checkpoint Created: 22/Mar/18  Updated: 13/Apr/18  Resolved: 13/Apr/18

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Judah Schvimer
Resolution: Won't Fix Votes: 0
Labels: rollback-non-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-34372 Drop collection command with majority... Closed
related to SERVER-34452 Wait for 2-phase drop to finish in tr... Closed
Sprint: Repl 2018-04-09, Repl 2018-04-23
Participants:

 Comments   
Comment by Spencer Brody (Inactive) [ 13/Apr/18 ]

We've decided not to do this for 4.0. We will leave constraint relaxation around during oplog application for now, until we are able to push two-phase drop behavior down into the storage engine.

Comment by Judah Schvimer [ 23/Mar/18 ]

As part of this ticket, we should remove relaxing NamespaceNotFound constraints and document validation constraints.

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