[SERVER-34452] Wait for 2-phase drop to finish in transaction tests Created: 13/Apr/18  Updated: 06/Dec/22  Resolved: 13/Apr/18

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

Type: Improvement Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
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
is related to SERVER-34349 Wait for drop to be majority committe... Closed
is related to SERVER-34069 Postpone 2nd phase of collection drop... Closed
Assigned Teams:
Replication
Participants:

 Description   

Collection 2-phase drop needs the DB lock in X mode which will block or abort the transactions, so we need to wait for them to be majority committed in SERVER-34349. However, this is not sufficient since the reaper runs asynchronously afterwards. We don't follow SERVER-34372 to complicate the logic of waiting for write concern. Instead, we will fix the tests for now and eventually with storage engine support, we don't have to acquire the DB lock in X mode to drop drop-pending collections.



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

We've decided to do SERVER-34372 after all, eliminating the need for any extra work in our tests.

Comment by A. Jesse Jiryu Davis [ 13/Apr/18 ]

I'm watching this ticket for the sake of drivers' tests too.

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