[SERVER-42025] Prevent Oldest timestamp from advancing in prepare_transaction_read_at_cluster_time.js. Created: 01/Jul/19 Updated: 29/Oct/23 Resolved: 19/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, 4.2.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Suganthi Mani |
| 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.2
|
||||||||
| Sprint: | Repl 2019-08-12, Repl 2019-08-26 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 10 | ||||||||
| Description |
|
prepare_transaction_read_at_cluster_time.js should run find command without query yielding else it can fail with "SnapshotTooOld" error due to race between updating the oldest timestamp in the storage and reopening of the snapshot after query yield. |
| Comments |
| Comment by Githook User [ 08/Nov/19 ] |
|
Author: {'username': 'smani87', 'email': 'suganthi.mani@mongodb.com', 'name': 'Suganthi Mani'}Message: (cherry picked from commit 54445c82d53a47b849247b22fc4e6ccbaf1a58d8) |
| Comment by Githook User [ 19/Aug/19 ] |
|
Author: {'username': 'smani87', 'email': 'suganthi.mani@mongodb.com', 'name': 'Suganthi Mani'}Message: |
| Comment by Suganthi Mani [ 08/Aug/19 ] |
|
Instead of query yielding, better option is to enable "WTPreserveSnapshotHistoryIndefinitely" failpoint for entire duration of the test which prevents node from advancing the oldestTimestamp. |