removeShard should hint about how to move data of tracked unsharded collections

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • v8.0
    • CAR Team 2024-12-23, CAR Team 2025-01-06, CAR Team 2025-01-20
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Removing a shard has two different phases: 1) draining all the data from the shard being removed and 2) commiting the operation.

      Right now we don't provide any hint about how to move the data of track unsharded collections: due to its current implementation their are considered as if they were sharded, waiting until their only chunk is "moved". However, this  won't happen as a regular sharded collection via moveChunk (and automatically done by the Balancer in most of the cases) but via moveCollection.

      The purpose of this ticket is to provide more useful information about which data is still pending to be moved and which operations are expected to be used.

            Assignee:
            Igor Praznik
            Reporter:
            Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: