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

DataReplicator initial sync should be resilient to applier failures

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.14
    • Affects Version/s: None
    • Component/s: Replication
    • Fully Compatible
    • ALL
    • Repl 2016-09-19, Repl 2016-10-10

      Currently if the applier has an error it will fassert and terminate the mongod. Some errors should probably be ignored and some should lead to a restart of initial sync.

      One example is here where an IndexOptionsConflict error led to an fassert. If this error had been ignored it probably would have been fine. Alternatively initial sync could have just restarted.
      https://logkeeper.mongodb.org/build/a3f0586facc3aafcdb1719977208c783/test/579fe5a89041300d28023a18

      At the very least we should restart initial sync on errors like this.

            Assignee:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: