[SERVER-46607] Hedged reads maxTimeMS expiration can cause the read error Created: 04/Mar/20  Updated: 29/Oct/23  Resolved: 05/Mar/20

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Misha Tyulenev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Service Arch 2020-03-09
Participants:

 Description   

The SERVER-46472 added a maxTimeMS set for hedged reads. This causes hedged commands to get MaxTimeMSExpired error when the hedged command expires.
The MaxTimeMSExipred error of the hedged read must be ignored in order to not interrupt the command.



 Comments   
Comment by Githook User [ 18/Mar/20 ]

Author:

{'name': 'Misha Tyulenev', 'username': 'mikety', 'email': 'misha@mongodb.com'}

Message: SERVER-46607 ignore MaxTimeMSExpire error on hedged reads

(cherry picked from commit a924cde8580dd00409a0c8296e81ff73709ad1a2)
Branch: v4.4
https://github.com/mongodb/mongo/commit/18128517432e6c4a7f9c9f5309e42366cab002e6

Comment by Githook User [ 05/Mar/20 ]

Author:

{'name': 'Misha Tyulenev', 'username': 'mikety', 'email': 'misha@mongodb.com'}

Message: SERVER-46607 ignore MaxTimeMSExpire error on hedged reads
Branch: master
https://github.com/mongodb/mongo/commit/a924cde8580dd00409a0c8296e81ff73709ad1a2

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