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

RefineCollectionShardKeyCoordinator should not use filtering metadata cache utilities to fetch routing information

XMLWordPrintableJSON

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

      The RefineCollectionShardKeyCoordinator requires up-to-date routing information to perform cross-shard validations on the refined shard key candidate, but it is using a method of the "Filtering Metadata Cache API" to obtain it.
      While this solution works today, SERVER-84243 will cause such logic not to work in the intended way.

            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: