[SERVER-86080] High value workloads on 3-shard cluster are only running weekly Created: 31/Jan/24  Updated: 06/Feb/24  Resolved: 06/Feb/24

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

Type: Task Priority: Major - P3
Reporter: Brad de Vlugt Assignee: Daniel Hill
Resolution: Fixed Votes: 0
Labels: neweng, perf-effort-small, perf-urgency-asap, perf-value-essential
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

This covers updating the cron so that the high value workloads on three shard run at the right frequency (every 4 hours for high value workloads).

See https://spruce.mongodb.com/task/sys_perf_perf_3_shard.arm.aws.2023_11_change_streams_latency_dc8b8fe1a242764c09bc5b0063fec3bd9918aaaf_24_01_24_23_54_12/tests?execution=0&sortBy=STATUS&sortDir=ASC for an example task that is only running weekly



 Comments   
Comment by Githook User [ 02/Feb/24 ]

Author:

{'name': 'Daniel Hill', 'email': 'dhhillaz@gmail.com', 'username': 'hilldani'}

Message: SERVER-86080: updated cron for high value workloads (#18620)

GitOrigin-RevId: a813ae0271911ee7405237c832c041a1a8171385
Branch: master
https://github.com/mongodb/mongo/commit/314f98db104a0de3314905062ea2e4b1a98f6307

Comment by Alice Doherty [ 01/Feb/24 ]

There's a couple things here that need to be looked at: 1.) The 3-shard cluster is defined as an anchor so we want to make sure we don't pass on the high-value-workload crons to other variants referencing that anchor (I assume that's why the crons were commented out in the first place? 2.) For some reason we're running all tests on the 3-Shard Cluster (QuerySettings) variant at the high-value frequency.

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