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

Jstestfuzz suite to introduce spurious write conflicts

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • v5.0, v4.4
    • Execution Team 2021-02-22, Execution Team 2021-03-08

    Description

      In an attempt to reproduce some failures, I noticed we have remarkably little coverage of handling spurious WriteConflicts, especially in operations where they are normally unexpected. While most of our code is designed to handle such cases, I think we should exercise these code paths more often, since WiredTiger can return WT_ROLLBACK at any time.

      I would suggest enabling the WTWriteConflictException and WTWriteConflictExceptionForReads fail points to a very low frequency (e.g. < 1%) so that most operations can make some progress.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-51593 Index build bulk builder does not handle WriteConflictExceptions

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-51526 Hybrid index builds can miss writes and crash in the event of a well-timed WriteConflictException

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-51656 CollectionBulkLoader does not handle write conflicts

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

          Task - A task that needs to be done. SERVER-21332 Add FSM runners that always enable the WTWriteConflictException failpoint

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

          Activity

            People

              bynn.lee@mongodb.com Bynn Lee
              louis.williams@mongodb.com Louis Williams
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: