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

Prepared commit race with moving stable timestamps

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Storage - Ra 2021-06-28, Storage - Ra 2021-10-18
    • Backport Requested:
      v5.0

      Description

      Mongodb relies on the all durable timestamp returned by wiredtiger to set the stable timestamp.

      It is computed as the minimum of the current global durable timestamp and the pinned durable timestamp of each transaction minus 1. However, the query process of querying the all durable timestamp and setting the stable timestamp is not atomic. So when we commit a prepared transaction, the stable timestamp can move ahead of its durable timestamp. This will cause the checkpoint to persist a partial of that transaction.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: