[SERVER-42489] Wait for commit point to advance before restarting node in oplog_replay_on_startup_with_bad_op.js Created: 29/Jul/19  Updated: 29/Oct/23  Resolved: 30/Jul/19

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

Type: Bug Priority: Major - P3
Reporter: Vesselina Ratcheva (Inactive) Assignee: Vesselina Ratcheva (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2019-08-12
Participants:
Linked BF Score: 15

 Description   

The test expects the stable timestamp to be at the top of the oplog when first shutting down the node. However, the stableTS is bounded by the commit point on EMRC=true servers, and the test does nothing to guarantee we have committed all our ops. The test should wait for the lastOpCommitted to reach the top of the oplog before restarting the node.



 Comments   
Comment by Githook User [ 30/Jul/19 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-42489 Wait for commit point to advance before restarting node in oplog_replay_on_startup_with_bad_op.js
Branch: master
https://github.com/mongodb/mongo/commit/81bb59c88daab629ee9bfdfccb6041e38c1f0440

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