[SERVER-25995] raise timeout for priority takeover in replsets_priority1.js Created: 07/Sep/16 Updated: 28/Feb/17 Resolved: 07/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.13, 3.3.14 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| 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 | ||||||||||||
| Backport Completed: | |||||||||||||
| Backport Requested: |
v3.0
|
||||||||||||
| Sprint: | Repl 2016-09-19 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
replsets_priority1.js only waits 60 seconds for a priority takeover; however, when only two nodes of a three node set are up, and the higher priority node (in secondary state) is behind the lower priority node (in primary state), and the higher priority node's sync source was previously the third node (that is now down), it can take quite a while for the higher priority node to switch sync sources, catch up, and successfully run for election as a priority takeover. |
| Comments |
| Comment by Githook User [ 28/Feb/17 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: (cherry picked from commit 5f438283aff7e36bd4d54f46066b2fe3926e599d) |
| Comment by Githook User [ 07/Sep/16 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |