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

Use only retriable version of clone command for movePrimary once 8.0 is last-lts

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Catalog and Routing

      SERVER-81229 added replay protection to the _shardsvrCloneCatalogData command, but considering mixed binaries environments, it added special handling to the NotARetriableWriteCommand error, retrying without the osi protection in case we encounter a shard that haven't been upgraded. Once 8.0 becomes last-lts, all binaries will have _shardsvrCloneCatalogData with replay protection, making the exception unnecessary.

      The purpose of this ticket is to remove that extra handling and using only the path that adds OSI protection to _shardsvrCloneCatalogData

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: