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

Update ConfigShardTransition hook to always move unsharded collections through moveCollection, not movePrimary

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2024-05-13, CAR Team 2024-05-27

      If an unsharded collection is created between the moveCollection and movePrimary issued by ConfigShardTransition hook, that collection will be moved by the movePrimary.

      The goal of this ticket is to make movePrimary fail with a transient error if it finds any unsharded collection (only for ConfigShardTransition) that the hook will handle and retry the operation starting again from moveCollection with all pending unsharded collections.

            Assignee:
            pol.pinol@mongodb.com Pol Pinol
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: