-
Type:
Improvement
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Replication
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
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.
- is related to
-
SERVER-34349 Wait for drop to be majority committed in transaction tests
-
- Closed
-
-
SERVER-34069 Postpone 2nd phase of collection drop until drop timestamp is in the stable checkpoint
-
- Closed
-
- related to
-
-
- Closed
-