[SERVER-57135] Race in abort_in_progress_transactions_on_step_up.js Created: 21/May/21 Updated: 12/Jan/22 Resolved: 12/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Samyukta Lanka |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Sprint: | Repl 2021-06-14, Repl 2021-06-28, Repl 2021-07-12, Repl 2021-07-26, Repl 2021-08-09, Repl 2021-08-23, Repl 2021-09-06, Repl 2021-09-20, Repl 2021-10-04, Repl 2021-10-18, Repl 2021-11-01, Replication 2021-11-15, Replication 2021-11-29, Replication 2021-12-13, Replication 2021-12-27, Replication 2022-01-10, Replication 2022-01-24 |
| Participants: |
| Description |
|
As part of the test, we stop replication on a node before we can replicate a specific document, but we want try to wait until the node has replicated the other documents. We check the node's last optime for this, which can race with updating the storage snapshot yet, so even though the node advances its lastApplied, it may not have updated the storage snapshot that serves reads, which means we won't be able to see the update when we query the transactions table. |