secondaries already possessing an index replicated via startIndexBuild oplog entry should vote for commit immediately

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • v4.4
    • Execution Team 2020-03-23
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This can occur if a simultaneous index build is run on the same index on a primary that a rolling index build only put on one or more secondaries.

      Prior to this ticket, receipt on a secondary of a startIndexBuild oplog entry for an index that the secondary already has will cause a crash. This is the more elegant solution.

            Assignee:
            Gregory Wlodarek
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: