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

Fail eviction if out of order handling races with checkpoint

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.1, 4.4.8, 5.0.2, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • 5
    • Storage - Ra 2020-06-01, Storage - Ra 2020-06-15, Storage - Ra 2020-11-30, Storage - Ra 2021-05-17, Storage - Ra 2021-06-14, Storage - Ra 2021-07-12

      For mixed mode transaction, we may see eviction concurrently removing records from the history store while we are still checkpointing the history store.

      Here's one scenario.

      Checkpoint runs on the page.

      We commit a mixed mode delete with timestamp 0.

      We commit another update on the key with a normal timestamp.

      Eviction runs on the page writing the new update to the disk and the 0 timestamp tombstone to the history store.

      The 0 timestamp tombstone causes all the history store content of that key being removed.

      Checkpoint runs on the history store.

            chenhao.qu@mongodb.com Chenhao Qu
            chenhao.qu@mongodb.com Chenhao Qu
            0 Vote for this issue
            16 Start watching this issue