make rollback_auth.js more robust

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.9
    • Affects Version/s: Needs Triage
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2018-10-08, Repl 2018-10-22, Repl 2018-11-05
    • 19
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      rollback_auth.js relies on nodes successfully completing rollback before performing auth checks and currently uses awaitReplication() to do so.

      Unfortunately, awaitReplication() does not guarantee that a node has rolled back especially in the case of network failures. We should explicitly check the state of the recovering node and make sure it is a secondary before performing these checks.

            Assignee:
            Pavithra Vetriselvan
            Reporter:
            Pavithra Vetriselvan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: