- 
    Type:
Task
 - 
    Resolution: Duplicate
 - 
    Priority:
Major - P3
 - 
    None
 - 
    Affects Version/s: None
 - 
    Component/s: None
 
- 
        Replication
 - 
        None
 
- 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 
It's hard to tell when diagnosing the root of a write conflict whether the mongodb layer transformed another error into a write conflict, or if the write conflict came from the storage engine, what the source of the write conflict is.
- duplicates
 - 
                    
SERVER-107546 Dump global WT state if too many write conflicts are hit in a row for the same transaction
-         
 - Closed
 
 -         
 
- is related to
 - 
                    
SERVER-76715 Log origin of WriteConflictException in writeConflictRetry()
-         
 - Closed
 
 -         
 
- related to
 - 
                    
SERVER-76774 Invariant that secondary oplog application doesn't get prepare conflicts
-         
 - Closed
 
 -