movePrimary leaves garbage on old db primary for tracked collections

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 5.0.0, 6.0.0, 7.0.0, 7.3.0-rc0, 8.0.0-rc0
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • 3
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The movePrimary operations does not clean the local catalog of the donor shard (old database primary) for tracked collections, it does it only for untracked collection.

      So if the old primary doesn't own any chunk for a specific collection, the movePrimary operations will leave the collection metadata in the local catalog for that shard.

              Assignee:
              Unassigned
              Reporter:
              Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: