[CDRIVER-1572] Does slow getaddrinfo cause spurious topology scan timeouts? Created: 30/Sep/16  Updated: 11/Sep/19  Resolved: 01/Nov/16

Status: Closed
Project: C Driver
Component/s: libmongoc, network
Affects Version/s: None
Fix Version/s: 1.5.0

Type: Task Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Does a bug like CDRIVER-1571 also manifest if a getaddrinfo call takes a long time?



 Comments   
Comment by A. Jesse Jiryu Davis [ 01/Nov/16 ]

The same work that fixed CDRIVER-1571 solved this, too. getaddrinfo is only called in the stream initiator, and the CDRIVER-1571 fix began the connectTimeoutMS clock after the stream initiator completes.

Generated at Wed Feb 07 21:12:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.