-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
RSS Sydney
-
200
Currently When write conflict happens we see log like this
[j0:s0:n1] {"t":{"$date":"2024-07-04T00:47:02.988+00:00"},"s":"I", "c":"WRITE", "id":4640401, "svc":"S", "ctx":"TransactionCoordinator","msg":"Caught WriteConflictException","attr":{"operation":"implicit collection creation","reason":"Caused by :: Collection namespace 'config.transaction_coordinators' is already in use. :: Please retry your operation or multi-document transaction.","namespace":"config.transaction_coordinators","attempts":0}}
it only logs the parent collection namespace, not the side collection namespace, even if the write conflict happened in the side collection, causing the whole transaction to abort and rolling back the parent collection writes. WC logs should include the actual namespace or at least the table name that encountered the write conflict. think about passing that table name info to this method and include it in reason field.
- is related to
-
SERVER-92019 Print write conflict log at logWriteConflictAndBackoff () in production build
- Closed