- 
    Type:
New Feature
 - 
    Resolution: Fixed
 - 
    Priority:
Major - P3
 - 
    Affects Version/s: None
 - 
    Component/s: Catalog, Concurrency
 - 
    None
 
- 
        Fully Compatible
 - 
        v4.4
 - 
        Execution Team 2019-12-30, Execution Team 2020-03-09, Execution Team 2020-03-23
 - 
        None
 
- 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 
This test should do a mix of operations both inside and outside of transactions that stress concurrency of DDL operations both within and outside of transactions.
Operations to test:
- update with {{upsert : true }}
 - insert
 - createIndexes
 - create, both with and without extra indexes beyond _id
 
Conditions to test:
- database, collection and indexes exist
 - database exists, but collection and indexes don't
 - database doesn't exist
 - test multiple operations on the same collection inside a multi-document transaction
 - test multiple operations on multiple collections inside a multi-doc transaction
 - test operations outside a multi-doc transactions
 - concurrent drop command (outside of transaction)
 
- is related to
 - 
                    
SERVER-46796 Specific errors during prepare should get propagated to the client
-         
 - Closed
 
 -         
 
- related to
 - 
                    
SERVER-46651 Concurrent update with upsert:true and dropCollection can error
-         
 - Backlog
 
 -