Refactor the existing methods to access the content of config.placementHistory

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-07-21, CAR Team 2025-08-04
    • None
    • 3
    • TBD
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      The config.placementHistory collection contains a log of namespace placement changes observed on the cluster over time, which change stream readers have to consult through a dedicated interface.

      SERVER-68929 originally introduced 3 methods to the ShardingCatalogClient as the API to allow the consumption of such content from any mongod/s node. These methods are nevertheless of scarse utility, considering that:

      • they act as mere passthrough methods for a dedicated config server method (introduced by SERVER-72872) which runs the business logic for querying config.placementHistory and ensuring proper serialization between read and reset requests of the log
      • their signature does not match the current needs of V2 change stream readers.

      The objective of this ticket is to:

      • Remove the existing interface from ShardingCatalogClient
      • Migrate from ShardingCatalogClientImpl to ShardingCatalogManager the aggregation logic to retrieve historical placement metadata.
      • Have the command handler directly invoke the ShardingCatalogManager.

              Assignee:
              Paolo Polato
              Reporter:
              Paolo Polato
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: