[SERVER-25564] backup_restore.js - increase timeout for hidden node and re-evaluate primary Created: 11/Aug/16 Updated: 25/Jan/17 Resolved: 11/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| 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 | ||||||||
| Sprint: | Repl 2016-08-29 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
on slow hosts, it may take longer than existing 60 seconds (the current timeout value) for the hidden node to transition to SECONDARY. Also, an election may happen while the hidden node is coming up, so we should re-evaluate the primary node for the remaining checks in the test script. |
| Comments |
| Comment by Githook User [ 11/Aug/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |