[GODRIVER-1694] Description update missing server address causing topology update to be discarded Created: 16/Jul/20  Updated: 20/Jul/20  Resolved: 20/Jul/20

Status: Closed
Project: Go Driver
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Suraj Narkhede Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates GODRIVER-1642 Ensure server descriptions always hav... Closed

 Description   

We noticed issues traffic was send to dead secondaries >60s after they died. I think the issue here is - 

There is no timeout set in the heartbeat loop for op.Execute. So it defaults to OperationTimeout set at the topology. If OperationTimeout is set to 60s, then it will take about 70-80s case for the heartbeat to finish with heatbeatTimeout and heartbeatInterval set to 10s.

We can use context with heartbeat timeout for the IsMaster command to finish the heartbeat faster.



 Comments   
Comment by Suraj Narkhede [ 16/Jul/20 ]

sorry for the duplicate bug. please resolve it. 

This bug was supposed to be missing address in description update causing topology to discard the update.

https://github.com/mongodb/mongo-go-driver/commit/81279aff197f6771395fca101cf58745819cbbf3#diff-cc0b094d8ce69672d7e2ff6da8ff60f5L234-R234

But it is fixed in 1.3.5.

Generated at Thu Feb 08 08:36:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.