[SERVER-6596] Secondary Acceptable Latency Threshold on mongos and mongo should match the drivers and the spec. Created: 25/Jul/12 Updated: 11/Jul/16 Resolved: 26/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.2.0-rc0 |
| Fix Version/s: | 2.2.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sam Kleinman (Inactive) | Assignee: | Ian Whalen (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
All drivers, and the specification, specify the acceptable threshold as 15ms, the server sets 10ms. These should agree to avoid confusing users who will see (slightly) different behaviors and results when using connections via the shell/mongos versus the drivers directly |
| Comments |
| Comment by auto [ 26/Jul/12 ] |
|
Author: {u'date': u'2012-07-26T14:28:21-07:00', u'email': u'ian.whalen@gmail.com', u'name': u'Ian Whalen'}Message: Merge pull request #271 from tychoish/secondary-latency-threshold
|
| Comment by auto [ 26/Jul/12 ] |
|
Author: {u'date': u'2012-07-25T13:32:59-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: |
| Comment by Sam Kleinman (Inactive) [ 25/Jul/12 ] |