Add an assert to make sure stable timestamp is not set to larger than the all_durable timestamp

XMLWordPrintableJSON

    • Type: Build Failure
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage - Ra 2020-10-19
    • 0

      One of the implicit contract of using prepared transaction in WiredTiger is that we cannot move stable timestamp ahead of the "all_durable" timestamp. Otherwise, the prepared transaction that is being committed may become stable as its durable timestamp is now behind the stable timestamp, which will cause the prepared transaction being partially visible to checkpoint.

      Add an assert to make sure we don't move the stable timestamp ahead of the all_durable timestamp.

            Assignee:
            Chenhao Qu
            Reporter:
            Chenhao Qu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: