Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-77966

Investigate tests which enable the skipClusterParameterRefresh failpoint

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • 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

    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.

      Attachments

        Activity

          People

            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            gabriel.marks@mongodb.com Gabriel Marks
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: