-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
The Server Discovery And Monitoring Spec has been updated: minHeartbeatFrequencyMS has changed from 10 ms to 500 ms. It is still not configurable (unless you're the Java Driver and you had a knob before the spec was written).
Based on recent experiences with replica set reconfig in MMS, and experiments performed with the Java Driver and MongoDB 3.0, we've decided that 500 ms is a safer value than 10 ms.
If a secondary is underpowered and collocated with other processes, then a huge number of clients calling ismaster every 10 ms might be able to make it less responsive, or delay the election, by overwhelming it while awaiting an election. The 500 ms number prevents a storm without unduly delaying the clients' notification when the election completes.
https://github.com/mongodb/specifications/commit/32901d
Future work may change this number again, or mandate exponential backoff, or rearchitect the method by which servers notify clients of topology changes.
- depends on
-
CXX-568 Change minHeartbeatFrequencyMS from 10 to 500
- Closed
-
CDRIVER-585 Change minHeartbeatFrequencyMS from 10 to 500
- Closed
-
CSHARP-1196 Change minHeartbeatFrequencyMS from 10 to 500
- Closed
-
CXX-566 Change minHeartbeatFrequencyMS from 10 to 500
- Closed
-
NODE-392 Change minHeartbeatFrequencyMS from 10 to 500
- Closed
-
PHPC-184 Change minHeartbeatFrequencyMS from 10 to 500
- Closed
-
PYTHON-866 Change MIN_HEARTBEAT_INTERVAL from 10ms to 500ms
- Closed
-
RUBY-879 Change minHeartbeatFrequencyMS from 10 to 500
- Closed