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

Fix largest_key failed to consider prepared update

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • WT10.0.1, 5.0.4, 5.2.0, 5.1.0-rc1, 4.4.11
    • None
    • None
    • 5
    • Storage - Ra 2021-10-18

    Description

      In a case, mongodb sees the largest key returns a prepared conflict error (link here). We should not return that error as the largest key should ignore all visibility check.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. WT-8241 Skip value return for largest key

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

          Improvement - An improvement or enhancement to an existing feature or task. WT-7992 Provide API to return the last key in a table regardless of visibility

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-58409 Startup RecordId initialization is flawed with durable history and reconstructing prepared transactions

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

          Activity

            People

              chenhao.qu@mongodb.com Chenhao Qu
              chenhao.qu@mongodb.com Chenhao Qu
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: