Do not check duplicate key constraints for index builds on secondaries

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.7
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2018-12-31, Storage NYC 2019-01-14
    • 6
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a background index build on a secondary finishes in the middle of a batch, while there are temporarily duplicate key violations on an index, it will fail.

      This did not used to be a problem, but now that we perform duplicate key checks at completion, this error is more likely to occur.

      This may involve taking the PBWM lock to so index build completion does not conflict with any replication batches.

            Assignee:
            Louis Williams
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: