[SERVER-61870] Retry loading oplog entries on CappedPositionLost in retryable_internal_transaction_test.js Created: 02/Dec/21 Updated: 29/Oct/23 Resolved: 22/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0, 5.2.0-rc3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-nyc-subteam3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v5.2
|
||||||||
| Sprint: | Sharding 2021-12-13, Sharding 2021-12-27 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 148 | ||||||||
| Description |
|
jstests/sharding/retryable_internal_transaction_test.js runs several test cases with a transaction larger than 16MB and loads the oplog entries generated by those tests for its assertions. If the oplog is truncated while the test is reading from it, the query will fail with CappedPositionLost and fail the test. Each test case only needs the oplog entries from the most recent large transaction, so it should be safe to retry on this error since the necessary oplog entries were likely not truncated. |
| Comments |
| Comment by Githook User [ 22/Dec/21 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit 1701a682db7a8548755d7fa8d50b8d712c17dadf) |
| Comment by Githook User [ 22/Dec/21 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |