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

Cloner can fail to create unique indexes on initial sync

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.0.6, 2.1.2
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • ALL

      For example, suppose the primary has a unique index on x. The primary has a document {_id:1, x:4}, deletes this document, and {_id:10000000, x:4} is inserted. In the meantime, a clone is happening, so the secondary clones {_id:1, x:4} before the delete happens, then {_id:10000000, x:4} at the end of the clone. Then it tries to build a unique index on x, which fails, because there are two docs with x:4.

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            kristina Kristina Chodorow (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: