[SERVER-22863] sharding read_after_optime.js test timeout should exceed ping interval Created: 25/Feb/16 Updated: 25/Jan/17 Resolved: 25/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.4, 3.3.3 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Completed: | |||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The balancer continually updates the config server. The interval used by the balancer needs to be taken in account when choosing an appropriate readConcern timeout for the test. To reproduce, change the maxTimeMS in this line from 5000 ms to some value larger than the ping interval (10 secs):
|
| Comments |
| Comment by Githook User [ 25/Feb/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: (cherry picked from commit 51ce259a38d2378e08355572d65d868844ce3324) |
| Comment by Githook User [ 25/Feb/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Randolph Tan [ 25/Feb/16 ] |
|
The balancer performs the ping regardless of whether the setting is ON or OFF. The shell helper for start/stop balancer relies on this behavior to make determine whether the balancer has seen the new setting. |
| Comment by Eric Milkie [ 25/Feb/16 ] |
|
I thought enabledBalancer defaulted to false now, in ShardingTest, unless you explicitly set it to true. |