Add write concern to copydb command

XMLWordPrintableJSON

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

      There should be a way to specify a write concern to be used after every insert in a copydb command, otherwise it's possible to overrun replication on the destination set, causing the secondaries to be too stale to catch up.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Spencer Brody (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: