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

Use executeDDLCoordinatorCommandAgainstDatabasePrimary when forwarding resharding requests from router to shard

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc16
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • v8.0, v7.3, v7.0
    • CAR Team 2024-08-05

      The resharding, moveCollection and unshardCollection commands on the router are calling into the primary shard by using executeCommandAgainstDatabasePrimary that attaches UNSHARDED placement version by default.

      Even though the attached version was not correct, this was fine until today because it was not being checked on the shard side. However, SERVER-92896 is soon going to add a check for timeseries in the command handler causing a version check (if present). Because of that, we should rely on executeDDLCoordinatorCommandAgainstDatabasePrimary that only attaches the database version.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: