[SERVER-28387] Extend secondary catchup period during stepdown in server-23299-1.js Created: 17/Mar/17 Updated: 06/Dec/17 Resolved: 21/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | Judah Schvimer |
| 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: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
In server-23299-1.js, there is at least one place where a primary is stepped down with a default secondaryCatchupPeriodSecs (https://github.com/mongodb/mongo/blob/ee0ff4acca5ac5704eb2208d3b58839c5ce0eb80/jstests/multiVersion/server-23299-1.js#L87). We should extend this to at least 60 seconds to allow for potentially slow nodes/machines that might still be catching up. Note that this test was deleted on 3.5 by commit https://github.com/mongodb/mongo/commit/eda82cb72e0271604267a9d80f5468d5b0dbc348 |
| Comments |
| Comment by Githook User [ 21/Apr/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |