Add a test to ensure on startup that the oplog is truncated correctly when the oplogTruncateAfterPoint equals the stable timestamp

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Replication
    • Execution Team 2020-06-29, Execution Team 2020-07-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-48934 fixed a bug where AutoGetCollectionForRead was being used in the replication recovery codepath for oplogTrunateAfterPoint. AutoGetCollectionForRead set a ReadSource on the operation that caused an old truncate after point value to be read.

      This ticket will add a regression test – splitting the work so that the bug fix can make it into the 4.4.0 release.

        1. wt-6411-repro.diff
          4 kB

            Assignee:
            Unassigned
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: