[SERVER-49017] Add a test to ensure on startup that the oplog is truncated correctly when the oplogTruncateAfterPoint equals the stable timestamp Created: 22/Jun/20  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File wt-6411-repro.diff    
Issue Links:
Backports
Depends
depends on SERVER-48934 Investigate replica set data mismatch... Closed
Assigned Teams:
Storage Execution
Backport Requested:
v4.4
Sprint: Execution Team 2020-06-29, Execution Team 2020-07-13
Participants:

 Description   

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.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 21/Jul/20 ]

I won't have the bandwidth for a while to investigate a testing behavior problem I ran into during CR, so I'm closing the CR and pushing the ticket out.

Generated at Thu Feb 08 05:18:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.