[SERVER-53459] rollback_all_op_types.js should ensure sync source's lastApplied > rollback node's lastApplied Created: 18/Dec/20 Updated: 29/Oct/23 Resolved: 09/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.23 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Samyukta Lanka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.4, v4.2, v4.0
|
||||||||
| Sprint: | Repl 2021-01-11, Repl 2021-01-25, Repl 2021-02-08, Repl 2021-02-22 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 22 | ||||||||
| Description |
|
We might need to explicitly call awaitPrimaryAppliedSurpassesRollbackApplied in rollback_all_op_types.js to wait for this. We should look into whether rollback_set_fcv.js and rollback_rename_count.js should do the same. |
| Comments |
| Comment by Githook User [ 09/Feb/21 ] |
|
Author: {'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}Message: |
| Comment by Samyukta Lanka [ 05/Feb/21 ] |
|
code review: https://mongodbcr.appspot.com/739200011/ |
| Comment by Samyukta Lanka [ 05/Feb/21 ] |
|
The original BF only happened on 4.0 with the in-memory storage engine. That's because in 4.0, the in-memory storage engine did not support recover to a stable timestamp. This behavior was changed in 4.2 in |
| Comment by Samyukta Lanka [ 18/Dec/20 ] |
|
This ticket should also investigate whether changes need to be made to the rollback fuzzer or the rollback deluxe test fixture if running on an inMemory storage engine |