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

Fix out of order handling of timestamp should consider stop timestamp as well

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • 0
    • Storage - Ra 2021-11-15

      The current logic of fixing the out of order timestamp only fix the update that has start timestamp larger than the out of order timestamp and it doesn't consider the update's stop timestamp. Therefore, an update with start timestamp smaller or equal to the out of order timestamp and stop timestamp larger than the out of order timestamp will be retained. However, such update will later be removed by rollback to stable because it's stop timestamp is larger than the onpage value. We should fix the stop timestamp of these records as well.

            Assignee:
            backlog-server-storage-engines Backlog - Storage Engines Team
            Reporter:
            chenhao.qu@mongodb.com Chenhao Qu
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: