[SERVER-77966] Investigate tests which enable the skipClusterParameterRefresh failpoint Created: 09/Jun/23  Updated: 05/Feb/24

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

Type: Task Priority: Major - P3
Reporter: Gabriel Marks Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: car-investigation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-74107 Fix interaction between audit synchro... Closed
Assigned Teams:
Catalog and Routing
Sprint: CAR Team 2023-11-27, CAR Team 2023-12-11, CAR Team 2023-12-25, CAR Team 2024-01-08, CAR Team 2024-01-22
Participants:

 Description   

Adding the internal transaction in the ClusterServerParameterRefresher caused bugs in a large number of telemetry tests and tests which use transactions and sessions. This is because these tests expect that the only transactions/sessions which exist are those created explicitly. This assumption is broken by the aforementioned refresher, which runs periodically and creates its own session and transaction. I used a failpoint, skipClusterParameterRefresh, to stop the refresher from running during these tests as a temporary measure, but these tests should be revisited to make them robust enough to handle these sorts of internally created transactions.


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