[SERVER-48756] Use larger maxTimeMSForHedgedReads hedging_metrics_server_status.js Created: 11/Jun/20  Updated: 29/Oct/23  Resolved: 15/Jun/20

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 4.4.0-rc10, 4.7.0

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

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Sharding 2020-06-15
Participants:
Linked BF Score: 28

 Description   

The test currently uses the maxTimeMSForHedgedReads of 10ms (the default is 150ms). This maxTimeMS is too short and can cause this assertion to fail since the request sent with the maxTimeMS can sometimes fail with maxTimeMSExpired so the numAdvantageouslyHedgedOperations will be 0 instead of 1.



 Comments   
Comment by Githook User [ 16/Jun/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-48756 Use larger maxTimeMSForHedgedReads hedging_metrics_server_status.js

(cherry picked from commit af4a4399ded235a268c631c59a231e8210e40192)
Branch: v4.4
https://github.com/mongodb/mongo/commit/608fa1638db44b8f1fb64653de8859a0256975fe

Comment by Githook User [ 15/Jun/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-48756 Use larger maxTimeMSForHedgedReads hedging_metrics_server_status.js
Branch: master
https://github.com/mongodb/mongo/commit/af4a4399ded235a268c631c59a231e8210e40192

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