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

Re-enable readConcern_atClusterTime_noop_write when tracking of unsharded collections is enabled

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2024-03-18, CAR Team 2024-04-01

      In SERVER-80135, an existing failure in this test was made more frequent. This failure can be seen in this BFG which is closed (I think erroneously) as part of an existing build failure.

      The problem seems to be related to a forced refresh happening on the primary triggered by one of the secondaries, though this hasn't been confirmed.

      Once the issue in the above BFG is understood and addressed, we should re-enable the test and consider increasing the number of nodes in the shards again.

            Assignee:
            enrico.golfieri@mongodb.com Enrico Golfieri
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: