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

Search shouldn't ignore globally visible tombstone of history store

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.2, 4.4.0-rc0, 4.7.0
    • Component/s: None
    • Labels:
      None
    • Story Points:
      3
    • Sprint:
      Storage Engines 2020-04-06, Storage - Ra 2020-04-20

      Description

      The following assert getting hit randomly while running the rollback_fuzzer_unclean_shutdown test.

              WT_ASSERT(session,
                (newer_hs_ts == WT_TS_NONE || hs_stop_ts <= newer_hs_ts || hs_start_ts == hs_stop_ts));
      

      The values of the variables in the assert statement are:
      newer_hs_ts - 6810105723700117506
      hs_start_ts - 6810105723700117506
      hs_stop_ts - 6810105723700117509

      From the above values, it seems that the order of the updates in the update chain before inserting them into the history store should be something like the following.

      update(6810105723700117506) -> Tombstone(6810105723700117509) -> update(6810105723700117506)

        Attachments

          Activity

            People

            Assignee:
            haribabu.kommi Haribabu Kommi
            Reporter:
            haribabu.kommi Haribabu Kommi
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: