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

Update importCollection to support collections that are logically the same, not just binary equivalents

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Catalog
    • None
    • Storage Execution

      Currently importCollection requires every .wt file to be binary equivalents on all nodes.

      A usage pattern we want to support for backup/restore using direct attach of a disk on each node, and letting recovery run on each node separately, prior to import. This prevents us from having to copy files around over the network.

      Using this pattern the collections will be logically the same, but the recovery process might have created binary differences in each wt file.

      If importCollection is run like this currently, we will run into the secondary nodes crashing because they fail the checksum against the export data provided by the primary during the import.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            peter.vertenten@mongodb.com Peter Vertenten
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: