[SERVER-58928] Have ReplicaSet test fixtures force mongod to take a stable checkpoint on test fixture startup Created: 28/Jul/21 Updated: 27/Oct/23 Resolved: 28/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jason Chan | Assignee: | Backlog - Replication Team |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
Currently, it's possible that if we write a jstests that kill a node and restart them before a stable checkpoint is taken. This leads to often unexpected initial syncs to happen when restarting the node because the WTRecoveryTimestamp will be null. |
| Comments |
| Comment by Jason Chan [ 28/Jul/21 ] |
|
Closing this out because the test infrastructure already does this here and here. The problem that I observed was actually because the jstest called rs.start() without setting restart: true, which will clear the data directory. |