Investigate tests which enable the skipClusterParameterRefresh failpoint

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 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, CAR Team 2024-08-05
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Marcos José Grillo Ramirez
              Reporter:
              Gabriel Marks
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: