[SERVER-68918] Unify how we perform no-op writes Created: 17/Aug/22  Updated: 12/Dec/23

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

Type: Improvement Priority: Major - P3
Reporter: Matt Broadstone Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: cs-subteam1, sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Cluster Scalability
Participants:

 Description   

We have a lot of similar code for performing a no-op write:

On initial inspection it seems like almost all of these cases could be replaced with a call to resharding::doNoopWrite. I'm not sure what the distinction between onOpMessage and onInternalOpMessage is. Also, some of these callers wrap the operation in a DBLock which does not appear to be required in all cases.

We should decide on a single helper for this, and reuse that helper where possible in the above linked locations.


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