[SERVER-6593] local ping time on nodes can take time to reach steady state Created: 25/Jul/12 Updated: 11/Jul/16 Resolved: 27/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client |
| Affects Version/s: | 2.2.0-rc0 |
| Fix Version/s: | 2.2.0-rc1 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Randolph Tan | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
We use a moving average of 4 samples to update the ping time for the nodes, so the stored ping time can initially be much smaller than the actual ping time (by a quarter at worst) of the replica node. |
| Comments |
| Comment by Randolph Tan [ 27/Aug/12 ] |
|
|
| Comment by Randolph Tan [ 27/Jul/12 ] |
|
Test written but cannot integrate to our automated test framework. See QA-112 for more details. Another approach is to conditionally insert sleeps in isMaster command processing at mongod using |
| Comment by auto [ 27/Jul/12 ] |
|
Author: {u'date': u'2012-07-25T11:25:13-07:00', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}Message: |