[SERVER-73295] Evaluate usefulness of hardcoded 10 seconds to expire chunks history Created: 25/Jan/23  Updated: 29/Nov/23  Resolved: 29/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: car-qw, oldshardingemea, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Catalog and Routing
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-02-20, CAR Team 2023-11-13, CAR Team 2023-11-27, CAR Team 2023-12-11
Participants:
Story Points: 1

 Description   

Historically, chunk history has had a life span of at least 10 seconds. Given that we usually expect both minSnapshotHistoryWindowInSeconds and transactionLifetimeLimitSeconds, this ticket is to evaluate the usefulness of keeping around the hardcoded 10 seconds.



 Comments   
Comment by Githook User [ 29/Nov/23 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-73295 Get rid of hardcoded 10 seconds to expire chunks history
Branch: master
https://github.com/mongodb/mongo/commit/e15fa9705dfff501ed927b0bf07e639305809236

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