[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:
Problem/Incident
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: SERVER-48038 mongos retries snapshot errors with new timestamp
Branch: master
https://github.com/mongodb/mongo/commit/9660d5d10118c18b54392c99bce62cb67d61e0ed

Comment by Githook User [ 26/May/20 ]

Author:

{'name': 'A. Jesse Jiryu Davis', 'email': 'jesse@mongodb.com', 'username': 'ajdavis'}

Message: SERVER-48038 mongos shouldn't retry SnapshotTooOld outside transaction
Branch: master
https://github.com/mongodb/mongo/commit/480333150950480a0e18e011cbe77174000ab046

Generated at Thu Feb 08 05:15:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.