Optimise the execution time of RenameCollectionParticipantService

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Sharding EMEA
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-71365 introduced a new check to verify if the process participating to a sharded renameCollection is also acting as the coordinator of the DDL, which is based on a remote query to the sharding catalog.

      Such remote query could be replaced with a local read of config.system.sharding_ddl_coordinators, looking for the document represents the state or the RenameCollectionCoordinator

              Assignee:
              [DO NOT USE] Backlog - Sharding EMEA
              Reporter:
              Paolo Polato
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: