[DOCS-5768] localThresholdMS option is not documented Created: 02/Jul/15 Updated: 11/Jan/17 Resolved: 12/Sep/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | drivers |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 30 weeks, 5 days ago | ||||||||
| Description |
|
While working on a support case, I was not able to find information about the localThresholdMS driver option anywhere in our documentation. The only place, which talks about it is this article. |
| Comments |
| Comment by A. Jesse Jiryu Davis [ 15/Jul/16 ] |
|
It is still documented with the deprecated name secondaryAcceptableLatencyMS over here: https://docs.mongodb.com/manual/core/read-preference-mechanics/#member-selection It's been localThresholdMS since we superseded the Read Preference Spec with david.golden's Server Selection Spec. |
| Comment by Sam Kleinman (Inactive) [ 02/Jul/15 ] |
|
The docs discuss this as "nearest" (i.e. http://docs.mongodb.org/manual/reference/read-preference/#nearest) using the last generation terminology. |
| Comment by Kaloian Manassiev [ 02/Jul/15 ] |
|
I am not talking about the server options, but about the driver one. It is called localThresholdMS. |
| Comment by Sam Kleinman (Inactive) [ 02/Jul/15 ] |
|
http://docs.mongodb.org/manual/reference/configuration-options/#replication.localPingThresholdMs |