[SERVER-85501] Investigate adding more structured way of testing ttl behavior in jstests/core Created: 19/Jan/24  Updated: 25/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Damian Wasilewicz Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-81927 Move noPassthrough timeseries tests i... Backlog
Assigned Teams:
Storage Execution
Participants:

 Description   

SERVER-81927 involves moving tests that do not depend on bucketing behavior from jstests/noPassthrough/timeseries into jstests/core/timeseries. However, it looks like a good number of these candidates (for example, jstests/noPassthrough/timeseries/timeseries_expire.js ) rely on setting the parameter for `ttlMonitorSleepSecs` to a lower value to test TTL behavior. Setting this parameter on the DB in sharded passthroughs will involve setting this parameter on a mongos, which will fail. 

It doesn't look like there is much TTL testing behavior in core - this ticket would involve creating a more structured way to set TTL behavior in core tests, which would make moving a number of timeseries tests into core easier and presumably increase coverage for TLL behavior.


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