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

Ignore IndexKeySpecsConflict error during initial sync oplog application

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.4
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • ALL
    • v8.0, v7.0, v6.0, v5.0
    • Repl 2024-08-05
    • 0

      Currently we ignore IndexAlreadyExists if we hit it during oplog application. We find a case in BF-34245 that an IndexKeySpecsConflict error can be thrown when the two index specs have the same key but different collation. We should also ignore this IndexKeySpecsConflict error. 

      We'd better add some comments to explain why these errors are fine to ignore.

            Assignee:
            jiawei.yang@mongodb.com Jiawei Yang
            Reporter:
            jiawei.yang@mongodb.com Jiawei Yang
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: