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

index build continues to enforce constraints after failing over from primary to secondary

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Execution Team 2019-11-18

      Indexing constraints are currently determined (enforced on primary; relaxed on secondary) at the start of an index build and stay intact throughout the life of an index build. With SERVER-44186, index builds are allowed to continue running in the background as a node steps down from primary to secondary. For unique indexes, inserting duplicate keys while the index build is in progress, this may cause the index builds to fail unexpectedly on the downgraded secondary.

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: