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

_configsvrCommitRefineCollectionShardKey test should wait for the metadata to be fully replicated

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0, 7.1.0-rc2
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v7.1
    • Sharding EMEA 2023-09-18
    • 35

      configsvr_commit_refine_collection_shard_key.js is doing a refresh in the shard in order to leave consistent metadata for the CheckShardFilteringMetadata hook, however, because there is no communication between the shard and the config server, the configOpTime is not being properly propagated, and if the refresh hits a secondary node that haven't replicated the metadata, we'll find inconsistencies when running the hook.

      We could wait for the config server to fully replicate the changes before issuing the refresh.

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: