[SERVER-35601] on startup setting of server parameter maxTargetSnapshotHistoryWindowInSeconds should also set targetSnapshotHistoryWindowInSeconds Created: 14/Jun/18  Updated: 29/Oct/23  Resolved: 27/Jun/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.1

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-34436 Workloads to apply transaction snapsh... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-07-02
Participants:

 Description   

In the code, targetSnapshotHistoryWindowInSeconds is initialized with the value of maxTargetSnapshotHistoryWindowInSeconds. I don't think runtime updates of maxTargetSnapshotWindowInSeconds should affect targetSnapshotHistoryWindowInSeconds, since it could adversely effect an already balanced system. But on startup is a clean slate with no cache pressure, and so should start with a full sized window and decrease as needed.



 Comments   
Comment by Githook User [ 27/Jun/18 ]

Author:

{'username': 'DiannaHohensee', 'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@10gen.com'}

Message: SERVER-35601 startup setting of maxTargetSnapshotHistoryWindowInSeconds should also set targetSnapshotHistoryWindowInSeconds
Branch: master
https://github.com/mongodb/mongo/commit/752069dbc79f22b6ae4691073d455d76c9bbf18d

Generated at Thu Feb 08 04:40:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.