[SERVER-28378] Extend secondary catch up period in priority_takeover_two_nodes_equal_priority.js Created: 17/Mar/17 Updated: 06/Dec/17 Resolved: 19/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.15, 3.4.6, 3.5.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | William Schultz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | bkp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v3.4, v3.2
|
||||||||
| Sprint: | Repl 2017-04-17, Repl 2017-05-08, Repl 2017-05-29 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The step down command in priority_takeover_two_nodes_equal_priority.js uses a default secondaryCatchupPeriodSecs value. We should extend it to at least 60 seconds to account for slow secondary machines. |
| Comments |
| Comment by Githook User [ 22/Jun/17 ] |
|
Author: {u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'}Message: (cherry picked from commit 344de09ffc51bbc7786269917ebd1b417b940a7a) |
| Comment by Githook User [ 22/Jun/17 ] |
|
Author: {u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'}Message: (cherry picked from commit 344de09ffc51bbc7786269917ebd1b417b940a7a) |
| Comment by William Schultz (Inactive) [ 19/May/17 ] |
|
The build failure linked to this ticket occurred on the 3.2 branch. |
| Comment by Githook User [ 19/May/17 ] |
|
Author: {u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'}Message: |
| Comment by Matthieu Rigal [ 07/Apr/17 ] |
|
Makes sense! |