-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
v4.0
-
Repl 2018-05-21, Repl 2018-06-04, Repl 2018-06-18
-
3
We want to test the interaction between transactions and collection drops. We should test the following cases:
- A transaction writes to a collection on one session. On a separate session, that a drop is attempted on that collection. The collection drop should block until either the transaction commits or maxTimeMS expires. We should also test this for dropDatabase.
- Create collections A and B. Start a transaction T by reading from a collection A. In a separate session, drop collection B. Then try to write to collection B in transaction T. Verify that this write fails, since the collection was dropped.
- related to
-
SERVER-34703 Write test for transactions with concurrent index drops and creates
- Closed
-
SERVER-34704 Write test for transactions on collections that are renamed concurrently
- Closed