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

After test_timestamp_abort run, cursor scan shows different results from cursor search

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None

      Description

      After looking at the data leftover after the failing run for WT-5916, we see an anomaly in the data files.  Each data file contains a range of keys (string-ified integers) like "1000000000" through "1000118532".  A program reading this could individually do WT_CURSOR->search for each key sequentially, or it could search to the first key and do WT_CURSOR->next(), and it should give the same results.  However, we see "extra" keys doing next() that we do not see with explicit calls to search.

       

        Attachments

        1. cmpdump.c
          5 kB
          Donald Anderson

          Activity

            People

            Assignee:
            backlog-server-storage-engines Backlog - Storage Engines Team
            Reporter:
            donald.anderson Donald Anderson
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: