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

Allow a failed changelog write in movePrimary's cleanupOnError to silently fail.

    XMLWordPrintable

Details

    • Fully Compatible
    • v4.0
    • Sharding 2019-01-28
    • 45

    Description

      The given contract for changelog writes is that these writes are "best-effort," implying that we should not assert on their success. This case in particular is problematic because it's inside a scopedGuard. When an exception is not caught from inside a scopedGuard, it causes std::terminate to be called.

      This ticket is to simply change the call from logChangeChecked to logChange, and then remove the uassertStatusOK.

      Attachments

        Issue Links

          Activity

            People

              blake.oler@mongodb.com Blake Oler
              blake.oler@mongodb.com Blake Oler
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: