[SERVER-74392] Investigate non-deterministic RPU count in retryable findAndModify Created: 27/Feb/23  Updated: 17/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Matt Broadstone Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Service Arch
Participants:

 Description   

The investigation in a recent support ticket identified non-determinism in billing metrics for a retryable findAndModify command. A retryable findAndModify operation will store a copy of the preimage in order to support transparent retries. The operation will perform an upsert in config.image_collection, keyed by the lsid. The current working theory is that something about the conditions in the test is occasionally triggering upsert, which requires an additional read which we are not filtering out of billing metrics. 

In this ticket, we should try develop a local reproducer so that we can improve our confidence in SERVER-73666 as a solution. 

 

 

 

 


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