Tenant migrations rely on an implicit listCollections ordering for cloning

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Today the tenant migration code performs two listCollections calls:

      The second stage is used so that we can resume the migration and continue where we left off. To do this it checks the local nodes collections and assumes the last entry of the command is the collection we were working on.

      However, there's currently nothing preventing listCollections from returning a different ordering of the collections which means that check would be wrong.

              Assignee:
              Unassigned
              Reporter:
              Jordi Olivares Provencio
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: