[SERVER-44726] Sys-perf: Resurrect initialsync-logkeeper on stable branches Created: 19/Nov/19  Updated: 06/Dec/22  Resolved: 05/Dec/19

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

Type: Task Priority: Major - P3
Reporter: Henrik Ingo (Inactive) Assignee: Backlog - Performance Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-44868 Initialsync logkeeper and logkeeper-s... Closed
Related
is related to SERVER-44868 Initialsync logkeeper and logkeeper-s... Closed
Assigned Teams:
Product Performance
Sprint: Performance 2019-12-30
Participants:

 Description   

We have disabled initialsync-logkeeper tests on older mongo branches, because the database snapshot only works on the two most recent versions due to the FCV check at MongoDB startup.

The old snapshots are still available in our EC2 account. It turns out we can point to the correct snapshot for each stable branch with a simple override in the dsi config. See https://evergreen.mongodb.com/task/sys_perf_3.6_linux_replSet_initialsync_logkeeper_initialsync_logkeeper_patch_5e92879d28b0687bd4831180739dedb0c34eae4b_5da9d3f1e3c3315c2c961e04_19_10_18_15_02_44 for an example.



 Comments   
Comment by Suganthi Mani [ 19/Nov/19 ]

If we plan to implement this ticket, it should help fixing the problem mentioned in PERF-1912.
CC david.daly

Comment by Robert Guo (Inactive) [ 19/Nov/19 ]

We're going to reassign this back to product-perf, STM doesn't own individual workloads in DSI but would be happy to help with infrastructure or features used across workloads.

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