Clone DDL keeps track of databases and collections cloned

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The clone DDL is run during an upgrade to clone all database and collection metadata to shards into the authoritative collections.

      If a stepdown occurs, the clone DDL should not start from scratch. It could persist a list of cloned collections, or the last processed index (always taking into account that the total number of collections and databases could exceed the 16 MB limit), in order to improve the non-happy path.

      If the cost of implementing this is low, we should do so to optimize the non-happy path.

            Assignee:
            Unassigned
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: