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

Make all logOp listeners rollback-safe

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.0.4, 3.1.0
    • Storage
    • None
    • Fully Compatible

    Description

      For now I'll make it a fatal error to rollback once you got to logOp, since today, once you get there, you shouldn't need to rollback.

      We will want to fix the listeners soon since the plan is that rollbacks will be able to happen at any time, but that can happen outside of the critical path of enabling rollback. The tricky listeners will be the role-graph adjuster and the sharding tracker of deletes for migrations.

      Attachments

        Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-17250 logOp rollback when legacy insert creates a namespace and then fails to insert the document (fatal assertion)

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-17265 thread convoys from WiredTigerRecoveryUnit::registerChange

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-18822 Sharded clusters with WiredTiger primaries may lose writes during chunk migration

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-30240 remove incorrect paragraph from getNextOpTime() comments in oplog.cpp

          • Trivial - P5 - Cosmetic problem like misspelt words or misaligned text.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-15774 findAndModify triggers rollback invariant failure with --notablescan

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-16322 Make sure that RecoveryUnit::commit() can safely throw WriteConflictException

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-17303 concurrent findAndModify ops with upsert: true can cause a fatal logOp() rollback

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-17198 logOp rollback in findAndModify when query for modified document fails (fatal assertion)

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-13896 Replace logOp() with a more operation-aware observer interface

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

          Activity

            People

              randolph@mongodb.com Randolph Tan
              mathias@mongodb.com Mathias Stearn
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: