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

IndexRebuilder should only restart index builds initiated internally

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.5.0
    • Component/s: Index Maintenance, Replication
    • Labels:
      None
    • Storage Execution
    • ALL

      It should not restart user-initiated index builds.

      Scenario:
      1) User starts building a unique index on {a:1} on the current primary, node A.
      2) Node A dies suddenly (kill -9 or power failure, etc) and node B becomes the new primary.
      3) Node A restarts and the IndexRebuilder restarts building of the index.

      At this point, node A now has an index that does not exist on the primary and never will. This would be less of a problem for a non-unique index, but because this is unique, an insert can now succeed on the primary but fail on node A, breaking replication.

      I think the right solution is to only rebuild indexes where we would not call logOp on completion.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            mathias@mongodb.com Mathias Stearn
            Votes:
            1 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: