Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-6224

Adding a globally visible tombstone when an on disk prepared update is rolled back

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • WT10.0.0, 4.4.0-rc7, 4.7.0
    • None
    • None
    • 5
    • Storage - Ra 2020-05-18

    Description

      This ticket was created out of WT-6165, it generally presents as a cache stuck as cursors are hung on prepare conflict. Essentially any cursor that attempts to read will get a prepare conflict on the related key and the cursor will hang. This will block eviction as the cursor will be pinning some amount of data, eventually causing a cache stuck.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. WT-6235 Change operation order of prepared commit and rollback

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. WT-6165 Fix cursor operation hung on WT_PREPARE_CONFLICT

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

          Bug - A problem which impairs or prevents the functions of the product. WT-6168 Ignore history store visibility when resolving prepared updates

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

          Build Failure - WT-6197 Cache stuck clean in test format (prepare)

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

          Activity

            People

              luke.pearson@mongodb.com Luke Pearson
              luke.pearson@mongodb.com Luke Pearson
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: