[SERVER-46992] Create JS test for v4.4-v4.2 oplogTruncateAfterPoint compatibility across v4.4 shutdown while primary Created: 19/Mar/20  Updated: 06/Dec/22  Resolved: 17/Aug/20

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

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

Issue Links:
Related
related to SERVER-46984 Stop async updates to the oplogTrunca... Closed
Assigned Teams:
Storage Execution
Participants:
Linked BF Score: 0

 Description   

This is related to a recent test failure (linked). We have multiversion coverage that caught an oplogTruncateAfterPoint bug across v4.4 binary shutdown and restart with v4.2 mongod binary. This task is just to make an explicit, so it's easier to diagnose. The test would be inherently racy, though, whether it catches new bugs.

Test:
v4.4
single node replica set with v4.4 binary – so that shutdown will eventually run while still primary
do some

{j:true}

writes against the primary – so that the oplogTruncateAfterPoint gets set
take a checkpoint that now includes the oplogTruncateAfterPoint – so startup recovery will have a checkpoint to use and run the truncate logic on finding the oplogTruncateAfterPoint
shut down the v4.4 mongod primary
v4.2
restart the node with a v4.2 binary
wait for the node to step up to primary – so that we know it is up and running, alive still.
Done


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