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

Don't write updates with different commit and durable timestamps to data store

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.4.0-rc0, 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • 5
    • Storage Engines 2020-02-24

      As we need to rollback the prepared updates in rollback to stable if its durable timestamp is larger than the stable timestamp (checkpoint timestamp) and we don't store durable timestamp in cell, we choose to not write the prepared updates with different commit timestamp and durable timestamp to data store if their durable timestamps are larger than the checkpoint timestamp as a temporary solution. BTW, it is OK to write them to the history store as we store their durable timestamps in the value.

      A proper fix for the problem of not storing durable timestamp in cell will be fixed in a follow on ticket.

            Assignee:
            chenhao.qu@mongodb.com Chenhao Qu
            Reporter:
            chenhao.qu@mongodb.com Chenhao Qu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: