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

Disable PeriodicShardedIndexConsistencyChecker during read_committed_lookup.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 7.0.13, 8.0.0-rc11
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0, v7.3, v7.0
    • Hide

      Repro in attached BF

      Show
      Repro in attached BF
    • CAR Team 2024-06-24, CAR Team 2024-07-08
    • 0

      The PeriodicShardedIndexConsistencyChecker runs an aggregation on secondary nodes of a shard. This secondary read can trigger a refresh if the secondary doesn't know the filtering information for the database.

      The read_committed_lookup test disables replication on both secondaries of one of the shards (one via a fail point and one because it is an arbiter) which will make the primary unable to refresh the catalog cache due to SERVER-78115 which introduced a majority write to ensure the primary is in fact primary.

      The test runs a lookup on the primary which will require the routing information for the collection we are doing a lookup from, which will get stuck behind the refresh which is waiting for majority write concern.

      Because this will be fixed by splitting the routing and filtering caches into two during SCAAR (SERVER-84243) and fixing this in the Shard Server Catalog Cache Loader would mean introducing a lot of logic for database refreshes (which we expect to be not very frequent), we will just fix the test to prevent the background refresh and wait for 8.1 to fix this.

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: