Initial replica set sync should clone from secondary

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 1.7.4
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When you add a new member to a replica set (or need to resync an existing member), it clones the data from the primary. This causes a performance impact. Instead, it would be better if the initial clone was take from a secondary so only the catchup running through the oplog need take place on the primary.

            Assignee:
            Kristina Chodorow (Inactive)
            Reporter:
            David Mytton
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: