[SERVER-49690] Retry "CappedPositionLost" when searching for old oplog entries Created: 17/Jul/20 Updated: 29/Oct/23 Resolved: 17/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.9, 4.4.1, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Charlie Swanson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v4.4, v4.2
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 9 | ||||||||||||||||
| Description |
|
The query plan may yield between the cursor establishment and iterating to retrieve the first result. During this yield it's possible for the oplog to "roll over" or shrink. This is rare, but if these both happen the cursor will be unable to resume after yielding and return a "CappedPositionLost" error. This can be safely retried. We should update some tests which search for old oplog entries to retry this error. |
| Comments |
| Comment by Githook User [ 06/Aug/20 ] |
|
Author: {'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}Message: (cherry picked from commit b58968562034c206cd041c083d1ac3cc5e749ec1) |
| Comment by Githook User [ 05/Aug/20 ] |
|
Author: {'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}Message: (cherry picked from commit b58968562034c206cd041c083d1ac3cc5e749ec1) |
| Comment by Githook User [ 17/Jul/20 ] |
|
Author: {'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}Message: |