do not exit with a non-zero code when shutting down a secondary

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 3.3.10
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 17 (07/15/16)
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, even if a write returns InterruptedAtShutdown, we fassert on a secondary. This causes the backup_restore.js test to fail, under certain workloads.

            Assignee:
            Eric Milkie
            Reporter:
            Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: