[SERVER-40490] ReplicaSetMonitor should check replicas at most twice per second Created: 05/Apr/19 Updated: 08/Jan/24 Resolved: 26/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | Shaileja Jain (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.2
|
||||||||
| Sprint: | Service Arch 2019-06-17, Service Arch 2019-07-01 | ||||||||
| Participants: | |||||||||
| Description |
|
Under some circumstances ReplicaSetMonitor can call isMaster on replica set members as fast as possible, instead of respecting the Server Discovery and Monitoring Spec's minHeartbeatFrequencyMS of 500ms. This risks overloading replicas and doesn't provide much benefit at detecting elections sooner. ReplicaSetMonitor should respect minHeartbeatFrequencyMS. |
| Comments |
| Comment by Githook User [ 26/Jun/19 ] |
|
Author: {'name': 'Shaileja Jain', 'email': 'shaileja.jain@gmail.com', 'username': 'shailejajain'}Message: |
| Comment by Gregory McKeon (Inactive) [ 15/Apr/19 ] |
|
We're not sure that 500ms is the correct amount of time, particularly given the increased speed of elections in recent versions. We should make this value configurable, and have Atlas test it with different values. This ticket is to make the value configurable and file a future ticket to work with Atlas to determine the right default. |