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

WT_UPDATE.type field can race with visibility checks when returning key/value pairs

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.2, 4.2.4, 4.3.4, 4.0.18, 3.6.19
    • Component/s: None
    • Labels:
      None
    • Story Points:
      13
    • Sprint:
      Storage Engines 2020-01-13, Storage Engines 2020-01-27, Storage Engines 2020-02-10
    • Backport Requested:
      v4.2, v4.0, v3.6

      Description

      Summary:

      Fix a race in walking the list of updates for a key.

       


      Running in develop, with the tightest proposed fixes for WT-5119, another failure:

      format.sh: /data/bostic/RUNDIR.5442 log:
          > t: process 51527 running
          > snapshot-isolation 0000081892.00/opqrstuvwxyzabcdefghi search mismatch
          > expected {}
          >    found {0000081892/LMN30303030303030303030303030303030303030303030303030303030303030303030srqponmlfedcbazyxzy}
          > 
          > t: run FAILED
          > snapshot-isolation error: Dumping page to /data/bostic/RUNDIR.5442/pagedump
          > snapshot-isolation error: Dumping LAS to /data/bostic/RUNDIR.5442/LASdump 

      This is actually the reverse of the typically WT-5119 failure, which makes me think it's something else entirely. The typical WT-5119 failure is "expected XXX, found nothing", and this is the opposite.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              keith.bostic Keith Bostic
              Reporter:
              keith.bostic Keith Bostic
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: