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

Relax checkHistoricalPlacementMetadataConsistency to tolerate the existence of resharding temp collections created through shardCollection

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

      SERVER-84384 recently changed the behaviour of the checkHistoricalPlacementMetadataConsistency() method for resharding temporary collections, so that

      • their metadata is expected to appear within config.collections and config.chunks, but not within config.placementHistory, as a consequence of how the server code implements reshardCollection
      • JS tests that forge resharding temporary collections (most commonly, by running shardCollection commands are considered logic that breaks such a rule (and are then expected to perform proper cleanup on test teardown, like here).

      Nevertheless, JS mutational fuzzer tests cannot be easily modified to comply with the above rule - and would hence need a relaxed version of checkHistoricalPlacementMetadataConsistency() .

            Assignee:
            paolo.polato@mongodb.com Paolo Polato
            Reporter:
            paolo.polato@mongodb.com Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: