[CSHARP-1128] Heartbeats should speed up to minHeartbeatFrequencyMS whenever any SelectServerAsync loop is waiting for a suitable server Created: 21/Nov/14  Updated: 02/Apr/15  Resolved: 26/Nov/14

Status: Closed
Project: C# Driver
Component/s: Connectivity
Affects Version/s: None
Fix Version/s: 2.0

Type: Bug Priority: Major - P3
Reporter: Robert Stam Assignee: Robert Stam
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

When SelectServerAsync does not find a suitable server, it triggers an early heartbeat to accelerate detection of topology changes that might result in a suitable server becoming available.

Heartbeats should occur at two frequencies:

1. heartbeatFrequencyMS: a slower heartbeat when everything is operating normally
2. minHeartbeatFrequencyMS: a faster heartbeat whenever some task was unable to find a suitable server and is waiting to see if a topology change results in a suitable server becoming available

But even when there are tasks waiting for a suitable server to appear, heartbeats must not be sent more frequently than minHeartbeatFrequencyMS.



 Comments   
Comment by Githook User [ 25/Nov/14 ]

Author:

{u'username': u'rstam', u'name': u'rstam', u'email': u'robert@robertstam.org'}

Message: CSHARP-1128: Added tests for HeartbeatDelay.
Branch: master
https://github.com/mongodb/mongo-csharp-driver/commit/0e75c2c41d33d28db4543a4aed8d6094131bfdfa

Comment by Githook User [ 25/Nov/14 ]

Author:

{u'username': u'rstam', u'name': u'rstam', u'email': u'robert@robertstam.org'}

Message: CSHARP-1128: Accelerate heartbeats when SelectServerAsync can't find a suitable server.
Branch: master
https://github.com/mongodb/mongo-csharp-driver/commit/566516d075619346fa4dc3a434971d80451f2e01

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