[SERVER-48038] Do not retry on SnapshotTooOld errors for snapshot reads outside of transactions on mongos Created: 08/May/20 Updated: 29/Oct/23 Resolved: 27/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Repl 2020-06-01 | ||||
| Participants: | |||||
| Linked BF Score: | 50 | ||||
| Description |
|
I think we currently retry on SnapshotTooOld errors on mongos (transactions have their own retry logic though based on canContinueOnSnapshotError). And we also seem to retry internally for find commands on mongos. This ticket is to make sure SnapshotTooOld errors are excluded from these retry behaviors (outside of transactions). |
| Comments |
| Comment by Githook User [ 26/May/20 ] |
|
Author: {'name': 'A. Jesse Jiryu Davis', 'email': 'jesse@mongodb.com', 'username': 'ajdavis'}Message: |
| Comment by Githook User [ 26/May/20 ] |
|
Author: {'name': 'A. Jesse Jiryu Davis', 'email': 'jesse@mongodb.com', 'username': 'ajdavis'}Message: |