[SERVER-74250] Rename slowOplogSamplingReads to slowCollectionSamplingReads Created: 22/Feb/23  Updated: 28/Feb/23

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

Type: Improvement Priority: Major - P3
Reporter: Jordi Olivares Provencio Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: neweng, tech-debt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-46870 Generalize the WiredTigerRecordStore:... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

SERVER-46870 Refactors the OplogStones into a generic CollectionTruncateMarkers class that can be reused in different implementations.

For testing there is a failpoint called slowOplogSamplingReads that can't be currently renamed to a more generic term until 7.0 is released due to multiversion testing.

The term should be something more generic called slowCollectionSamplingReads.

The places affected by this have been mamrked with TODOs in the code with this server ticket.



 Comments   
Comment by Haley Connelly [ 23/Feb/23 ]

Good point, sorry I misread it was a server parameter

Comment by Jordi Olivares Provencio [ 23/Feb/23 ]

This is a failpoint rename so I don't expect users to actually interact with it

Comment by Haley Connelly [ 23/Feb/23 ]

Has there been discussion about this with product? I'm curious as to whether we want to keep our oplog sampling at a separate granularity

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