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

improve exception handling in SyncTail::oplogApplication()

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0
    • Sprint:
      Repl 2018-05-21, Repl 2018-06-04, Repl 2018-06-18
    • Linked BF Score:
      50

      Description

      unexpected exceptions in SyncTail;:oplogApplication may sometimes cause OpQueueBatcher to terminate early and trigger the invariant on the _isDead field. We should consider more graceful shutdown semantics for the OpQueueBatcher or handle exceptions in oplogApplication() explicitly. This issue affects 3.4 through 3.6

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-25240 set_terminate() should be done for every thread under Windows

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. SERVER-32913 Parallelize application of applyOps oplog entries

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-25071 Ensure replication batch finishes before shutdown

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              benety.goh Benety Goh
              Reporter:
              benety.goh Benety Goh
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: