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

replica set sync halts on dup key when using upserts on a collection with a unique index

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major - P3 Major - P3
    • None
    • 2.0.0
    • Replication
    • None
    • linux 64bit
    • ALL

    Description

      In a replica-set with 2 data nodes an one arbiter
      I do upserts in a collection having a unique index on a field
      all works as expected on primary, 2nd upsert on same index value replaces the first one. But rs.status() reports dup key on secondary.

      doing a full resync of secondary did'nt help: error reappears with next upsert.

      As a workaround, I added remove before upsert and have no longer sync errors.

      Attachments

        Activity

          People

            Unassigned Unassigned
            pascal.masschelier@gmail.com Pascal Masschelier
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: