[SERVER-78929] WriteConflict counter in serverStatus is not ticked if it is thrown by transaction Created: 13/Jul/23  Updated: 31/Oct/23  Resolved: 31/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Wenbin Zhu Assignee: Wei Hu
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-56706 Metric to count multi-document transa... Closed
Assigned Teams:
Storage Execution
Operating System: ALL
Sprint: Execution Team 2023-11-13
Participants:

 Description   

As opposed to non-transactional writes, when a multi-statement transaction throws a writeConflict, we don't increment the writeConflicts counter in serverStatus. This can be confusing for end users since driver automatically retries transactions on writeConflicts (imagine a user sees writeConflictExceptions in a transaction being logged or even popped up to application when driver exhausts retry, but then finds out that the writeConflict counter is not updated).



 Comments   
Comment by Wei Hu [ 31/Oct/23 ]

Confirmed with wenbin.zhu@mongodb.com this is a duplicate of SERVER-56706.

Generated at Thu Feb 08 06:39:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.