[SERVER-54157] Missing timeout mechanism in RSM findHost function call Created: 30/Jan/21  Updated: 29/Oct/23  Resolved: 07/Apr/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: Sharding-NYC, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4, v4.2, v4.0
Sprint: Sharding 2021-02-22, Sharding 2021-03-08, Sharding 2021-03-22, Sharding 2021-04-05, Sharding 2021-04-19
Participants:
Linked BF Score: 39

 Description   

The goal of this ticket is to add/enforce a timeout mechanism to this RSM findHost function call.

Two months ago that function call was properly protected. It seems that this issue was introduced when we added the CancelationToken to some of the RSM functions.



 Comments   
Comment by Githook User [ 07/Apr/21 ]

Author:

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

Message: SERVER-54157 Remove maxWait from comments for findHost and getHostOrRefresh
Branch: master
https://github.com/mongodb/mongo/commit/c2566e29b96559ac5ba4c8616a357c4025a0f843

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