[DRIVERS-340] Make minimum value of maxStalenessSeconds 90 seconds Created: 21/Nov/16 Updated: 25/Oct/19 Resolved: 08/Dec/16 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Rathi Gnanasekaran | Assignee: | Rathi Gnanasekaran |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
This supersedes
These parts of
Now, to complete this ticket:
|
| Comments |
| Comment by Danny Hatcher (Inactive) [ 25/Oct/19 ] |
|
bartle, this ticket is the result of an update to our Max Staleness Specification. The rationale for the minimum value of 90 is explained in the subsection Smallest allowed value for maxStalenessSeconds. If you still have concerns with the setting after reading our justification, would you mind creating a new DRIVERS ticket? The work on this ticket was finished in 2016 so any future work would rely on another ticket anyway. |
| Comment by David Bartley [ 24/Oct/19 ] |
|
Is there any rationale for requiring maxStalenessSeconds be at least 90s? It's possible to tune heartbeatFrequencyMS in drivers. It's not possible to tune idleWritePeriodMS in drivers, but it is now possible to tune periodicNoopIntervalSecs in the server, so arguably idleWritePeriodMS should be discovered (presumably isMaster would return the server value or something). Either way, if you run a replset in a single region, you're looking at milliseconds of latency and lag, so 90s is orders of magnitude away reality. |
| Comment by Rathi Gnanasekaran [ 08/Dec/16 ] |
|
Closing ticket as all linked tickets are resolved. |