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

Consider checkpoint timestamp when updating the pinned timestamp

    XMLWordPrintable

Details

    • Technical Debt
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • None
    • None
    • 5
    • Storage - Ra 2022-02-07

    Description

      Summary
      Currently, when we are updating the pinned timestamp, we are not considering the checkpoint timestamp. We consider the checkpoint timestamp only when we check the global visibility. This is because we want to the pinned content to be as small as possible in memory before durable history. Now with durable history, there is no need to do that. We can directly consider checkpoint timestamp when we updating the pinned timestamp.

      Motivation

      • Does this affect any team outside of WT?

      No

      • How likely is it that this use case or problem will occur?

      N/A

      • If the problem does occur, what are the consequences and how severe are they?

      N/A

      • Is this issue urgent?

      No

      Acceptance Criteria (Definition of Done)

      Pass mongodb patch build and stress test.

      • Testing

      Use existing testing

      • Documentation update

      N/A

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: