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

createIndex should add an entry in oplog even if the index exists

    • Type: Icon: New Feature New Feature
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • None
    • Storage Execution
    • Repl 2017-01-23, Repl 2017-02-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When an index is built in a rolling fashion (by taking nodes out of a replica set one by one and building the index on them) as described in Build Indexes on Replica Sets, an oplog entry never gets created and the index doesn't get created on the backup. There is currently no safe workaround to create such indexes on backup and the only available solution is a resync of backup which could be very long.

      Could we have a way to create an entry in oplog for indexes that already exist and have secondaries (including backup) only create that index if it's not already there?

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            amar.hamzeh@mongodb.com Amar Hamzeh
            Votes:
            0 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved: