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

minValid on another branch of history is unrecoverable but not detected

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • Repl 2020-08-10, Repl 2020-08-24
    • 20

      With enable-majority-read-concern false (EMRC=false), we may have a failure during rollback, when the rollback source was on a branch of history which is ultimately rolled back itself. This results in the minValid document on the failed node being on the wrong branch of history. If no sync source still has this branch of history, the situation is unrecoverable, but we do not detect this.

      It's not 100% clear how we would; we could see if no nodes had the requiredOpTime and if so declare it unrecoverable, but this wouldn't solve the BF because one node was unreachable at the time.

            matthew.russotto@mongodb.com Matthew Russotto
            matthew.russotto@mongodb.com Matthew Russotto
            0 Vote for this issue
            3 Start watching this issue